Unkillable runaway tcsh thread ?

michaelsanford

Translator, Web Developer
It seems that after I issue a "sudo fink purge XXX" and that thread terminates, I get a tcsh (my default shell) thread using 80% of my CPU that I can't kill (sudo kill PID doesn't do anything, and doesn't return any errors).

Is that a leftover of purge doing some stuff that I should let finish or should I reboot, like I did last night ?

It's been abuot 2 hours since it's bee going, and my CPU monitor reports about 50/50 system and user usage with only Safari open.
 
michaelsanford said:
It seems that after I issue a "sudo fink purge XXX" and that thread terminates, I get a tcsh (my default shell) thread using 80% of my CPU that I can't kill (sudo kill PID doesn't do anything, and doesn't return any errors).

Is that a leftover of purge doing some stuff that I should let finish or should I reboot, like I did last night ?

It's been abuot 2 hours since it's bee going, and my CPU monitor reports about 50/50 system and user usage with only Safari open.

try: sudo kill -9 PID
 
Yeah, the -9 option to kill should kill it. Just doing kill PID sends the -15 option by default. Difference is the -9 option is the kill signal (non negotiable, you might say), while a process has the option of ignoring the -15 (TERM) signal.
 
Back
Top