[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [leafnode-list] Cannot obtain lock file, aborting.
On 15 Nov 2002, Clemens Fischer wrote:
> "Michael O'Quinn" <michael@xxxxxxxxxxx>:
>
> > Well now, that's a different matter. I would try gently killing
> > that process first "kill -HUP 4832". If that doesn't work then chop
> > off it's head "kill -9 4832" If THAT doesn't kill it, something's
> > likely wrong with your system.
>
> you must verify that this process responds to a HUP and does the right
> thing. many programs take a variety of signals making them do
> different things. your recipe is much too simple. eg. most of the
> time a daemon will reread its configuration but stay alive and well on
> a HUP. if you then -KILL it, you may make things worse, if it wasn't
> designed to handle it. i mean, instead of KILL the man page might
> tell you which signal to send to get it to die gracefully.
This territory has already been covered.
Unless I'm completely blowing smoke, "kill -HUP" IS the way to gracefully
stop fetchnews.
Care to comment Matthias?
Michael
--
leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx -- mailing list for leafnode
To unsubscribe, send mail with "unsubscribe" in the subject to the list