On Fri, 25 Mar 2005, Harry Putnam wrote:
I've been monkeying around with metalog. Configuring and looking at init scripts. I'm finding that after a few starts and stops the normal /etc/init.d/metalog start/stop doens't work. I just get a message that metalog is already running. Asking for `stop' it reports `metalog not stopped'.
Checking /var/run... I see no pid for metalog ps wwaux|grep metalog doesn't turn up a daemon pid.
I had a similar thing happen with sendmail yesterday and finally rebooted to get it stopped and back on track to where /etc/init.d/sendmail start/stop/restart/status would work.
There must be a way to get metalog lined out without a reboot. killall metalog doesn't do it either.
With init scripts, you can often check status of a service using "status" instead of start. You can also say "zap" to mark a service as stopped, i.e.:
/etc/init.d/metalog zap
Thanks... the `zap' got it straightened out. Seems it would be a good idea to include a comment about `zap' in the initscripts in /etc/init.d.
-- [email protected] mailing list
