cheers vox, got impatient though and rebooted, hah! couldn't mount this time, had to reboot the other box - again! i'm hoping that maybe adding 'intr' to the fstab line might help in future? with umount -l, although the mount point is lo longer attached, there will still be hung processes, the ones responsible for 'device busy' messages?
bascule On Tuesday 24 September 2002 3:47 am, you wrote: > 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 -- 'Have you lost your senses?' 'Yes, but I may have found some better ones.' (Interesting Times)
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
