I'd like to figure out a way to "assassinate" processes that get stuck in the "waiting IO" state when I know there's no way they'll ever come out of that state. I just had to reboot my linux workstation to resolve such an issue. I had an file system containing mp3's mounted via smbfs. Unknown to me, this connection had become stale, so when I started up xmms, it hung and immediately went into the dreaded "waiting IO" state, while holding onto my sound hardware. I did a df and had that stuck as well, along with the bash shell I spawned it from. I think I'd like to write a "SIGMURDER" signal that would tell the kernel to just through its tables and forcibly unallocate all the resources a particular process is holding, close all its handles, etc. So before I even contemplate this endeavor, is their away to already do this? Thanks, Tim.
heh i encounter the same problem all the time i mount my mp3s via samba and then my windows box reboots. samba freaks the mount and processes get fucked in the ass. here is how i solve it ... drop all packets to your windows machine long enough to kill all the offending processes and umount the drive. iptables -I INPUT 1 -d WINDOWS -j DROP or if thats a prob (like you're ssh-ing from your windows machine :D), add in -p TCP --dport 139 -mike ----- Original Message ----- From: "Keller, Tim" <Tim.Keller@stratus.com> To: <wlug@wlug.org> Sent: Friday, March 08, 2002 09:38 Subject: [Wlug] itch to scratch...
I'd like to figure out a way to "assassinate" processes that get stuck in the "waiting IO" state when I know there's no way they'll ever come out of that state.
I just had to reboot my linux workstation to resolve such an issue. I had an file system containing mp3's mounted via smbfs. Unknown to me, this connection had become stale, so when I started up xmms, it hung and immediately went into the dreaded "waiting IO" state, while holding onto my sound hardware. I did a df and had that stuck as well, along with the bash shell I spawned it from.
I think I'd like to write a "SIGMURDER" signal that would tell the kernel to just through its tables and forcibly unallocate all the resources a particular process is holding, close all its handles, etc.
So before I even contemplate this endeavor, is their away to already do this?
Thanks, Tim. _______________________________________________ Wlug mailing list Wlug@mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug
participants (2)
-
Keller, Tim
-
Michael Frysinger