Red Hat Bugzilla – Bug 459613
anacron.init references /var/run/anacron.pid pidfile, but anacron doesn't generate it
Last modified: 2008-08-26 03:08:12 EDT
SSIA, the init script should only list a pid file if the daemon in fact creates one. System-config-services relies on the init script metadata to be accurate, otherwise it might not detect status changes properly.
There's an easy and hard way to do it:
Easy: remove the "# pidfile: ..." line from anacron.init
Hard: make anacron write said pidfile
I prefer the last one because it lets system-config-services detect if the service crashes and reflect that in the services list.
That's not appropriate fix. Anacron is really creating a pidfile, but it exists only as long as anacron has something to do. If I remove pidfile from init script then anacron daemon looks like stopped all the time.
I see... Perhaps we need a way to flag services as "one-off" instead of long-running so this can be distinguished in the GUI. Do you think we should discuss this here or on fedora-devel-list?
Maybe we should check for all "strange" services and mark them "one-off". The discussion on fedora-devel would be nice.