public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Edenfield <kutulu@kutulu.org>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] dhcpd always shows "crashed" even though it's running
Date: Thu, 3 Sep 2015 20:09:02 -0400	[thread overview]
Message-ID: <55E8E11E.5030103@kutulu.org> (raw)

For some reason, whenever I check the status of my startup scripts, 
dhcpd registers as "crashed". However, dhcpd is up and running and 
working fine. Normally I don't worry about it, but on those occasions 
where dhcpd does stop working, it's hard to tell if it's "fixed" or not.

What makes rc-status think something is crashed, and how can I fix this?

basement log # rc-status -v | grep crashed
  dhcpd [  crashed  ]
basement log # ps aux | grep dhcpd
root      2214  0.0  0.0   8268   876 pts/0    S+   19:47   0:00 grep 
--colour=auto dhcpd
dhcp      2648  0.0  0.6  30028 12136 ?        Ss   Aug29   0:00 
/usr/sbin/dhcpd -cf /etc/dhcp/dhcpd.conf -q -pf /var/run/dhcp/dhcpd.pid 
-lf /var/lib/dhcp/dhcpd.leases -user dhcp -group dhcp -chroot 
/chroot/dhcp enp0s7



             reply	other threads:[~2015-09-04  0:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-04  0:09 Mike Edenfield [this message]
2015-09-04  0:59 ` [gentoo-user] dhcpd always shows "crashed" even though it's running Fernando Rodriguez
2015-09-04  1:47   ` Dale
2015-09-04  2:12     ` Fernando Rodriguez
2015-09-04  2:46       ` Dale
2015-09-04  7:06         ` Mick
2015-09-04  8:48           ` Neil Bothwick
2015-09-04  9:10             ` Mick
2015-09-04  9:31               ` Neil Bothwick
2015-09-04  9:16           ` Fernando Rodriguez
2015-09-05 16:43           ` Mike Edenfield
2015-09-04 11:25   ` Mike Edenfield
2015-09-04 19:28     ` Fernando Rodriguez
2015-09-04  1:24 ` Rich Freeman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55E8E11E.5030103@kutulu.org \
    --to=kutulu@kutulu.org \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox