On Thu, Sep 3, 2015 at 8:09 PM, Mike Edenfield <kut...@kutulu.org> wrote: > 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? >
Not to sidetrack the discussion, but this is one of the areas where systemd does shine, in a sense. If systemd thinks the service is down, it is definitely down, because by default when systemd thinks a service is down it kills anything it ever spawned (and it can auto-restart if configured to do so). So, this forces to you configure the unit correctly so that you don't have these kinds of maybe-running-maybe-not situations. It is a bit like having strong types and stricter build-time error checking. It makes it a little harder to be lazier but saves you as the user from the lazy developer. As far as openrc goes, I suspect it is a pid file issue of some kind. If a process goes and forks without putting the right pid in the file then there is no way for openrc to detect this. -- Rich
