Re: kill won't kill
Bill schrieb: > On Linux systems I frequently use ``strace -p pid'' to see what > a process is doing. I don't know the FreeBSD equivalent of strace. strace is not a program that is dedicated to Linux. You can use strace with FreeBSD too. You only need to install it and mount procfs: # pkg_add -r strace # mount_procfs procfs /proc Regards Björn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kill won't kill
Bill Campbell wrote:
On Sun, May 20, 2007, Remko Cijffers wrote:
Hi,
I'm running a python script which has stopped responding. Killing off
the process doesn't work:
# ps -ax | grep nzb | grep -v grep
48426 p1 TLs 136:51.62 /usr/local/bin/python /usr/local/bin/hellanzb.py
# kill -SIGKILL 48426
# ps -ax | grep nzb | grep -v grep
48426 p1 TLs 136:51.62 /usr/local/bin/python /usr/local/bin/hellanzb.py
The only tip I could find seems to reference the 'wait for lock' flag
('L' in ps output). A lock could come from samba but restarting the
daemon doesn't solve the problem.
Typically unkillable processes are the result of hanging on some file or
device that's waiting on kernel services which never return.
Using ``lsof -p pid'' to see that the process is using at may give a hint
as to what it's hanging on.
On Linux systems I frequently use ``strace -p pid'' to see what a process
is doing. I don't know the FreeBSD equivalent of strace.
Bill
--
INTERNET: [EMAIL PROTECTED] Bill Campbell; Celestial Software LLC
URL: http://www.celestial.com/ PO Box 820; 6641 E. Mercer Way
FAX:(206) 232-9186 Mercer Island, WA 98040-0820; (206) 236-1676
``We maintain that the very foundation of our way of life is what we call
free enterprise,'' said Cash McCall, "but when one of our citizens
show enough free enterprise to pile up a little of that profit, we do
our best to make him feel that he ought to be ashamed of himself."
-- Cameron Hawley
That would be truss(1).
strace is also in ports if you prefer to use it.
-Garrett
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kill won't kill
On Sun, May 20, 2007, Remko Cijffers wrote:
>Hi,
>
>I'm running a python script which has stopped responding. Killing off
>the process doesn't work:
>
>># ps -ax | grep nzb | grep -v grep
>>48426 p1 TLs 136:51.62 /usr/local/bin/python /usr/local/bin/hellanzb.py
>># kill -SIGKILL 48426
>># ps -ax | grep nzb | grep -v grep
>>48426 p1 TLs 136:51.62 /usr/local/bin/python /usr/local/bin/hellanzb.py
>
>The only tip I could find seems to reference the 'wait for lock' flag
>('L' in ps output). A lock could come from samba but restarting the
>daemon doesn't solve the problem.
Typically unkillable processes are the result of hanging on some file or
device that's waiting on kernel services which never return.
Using ``lsof -p pid'' to see that the process is using at may give a hint
as to what it's hanging on.
On Linux systems I frequently use ``strace -p pid'' to see what a process
is doing. I don't know the FreeBSD equivalent of strace.
Bill
--
INTERNET: [EMAIL PROTECTED] Bill Campbell; Celestial Software LLC
URL: http://www.celestial.com/ PO Box 820; 6641 E. Mercer Way
FAX:(206) 232-9186 Mercer Island, WA 98040-0820; (206) 236-1676
``We maintain that the very foundation of our way of life is what we call
free enterprise,'' said Cash McCall, "but when one of our citizens
show enough free enterprise to pile up a little of that profit, we do
our best to make him feel that he ought to be ashamed of himself."
-- Cameron Hawley
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
kill won't kill
Hi,
I'm running a python script which has stopped responding. Killing off
the process doesn't work:
# ps -ax | grep nzb | grep -v grep
48426 p1 TLs 136:51.62 /usr/local/bin/python /usr/local/bin/hellanzb.py
# kill -SIGKILL 48426
# ps -ax | grep nzb | grep -v grep
48426 p1 TLs 136:51.62 /usr/local/bin/python /usr/local/bin/hellanzb.py
The only tip I could find seems to reference the 'wait for lock' flag
('L' in ps output). A lock could come from samba but restarting the
daemon doesn't solve the problem.
Anyone any idea's?
Greetings,
Remko
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
