bascule <[EMAIL PROTECTED]> writes: > the process in question is: > 040 500 32629 1 9 0 26112 10620 lock_p D ? 0:00 xmms > as you can see, apparently the parent process is 1 i.e. init killing this > defeats the objectm which is to not reboot! > > the lock_p and D look interesting, xmms was playing files on an nfs > share from another machine, this box crashed and although it's back > up and sharing again, i cn not access the mount point or unmount > that mount point, i'm assuming that if i can succed in that then i > can deal with xmms?
Probably. Do an "umount -l /whatever/mountpoint" and then try to mount it again, see if that helps. Vox -- Pain is the gift of the gods, and I'm the one they chose as their messenger.... For info on safety in the BDSM lifestyle http://www.the-vox.com Think of the Linux community as a niche economy isolated by its beliefs. Kind of like the Amish, except that our religion requires us to use _higher_ technology than everyone else. -- Donald B. Marti Jr.
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
