just the info i needed, thanks:-)
bascule
On Tuesday 24 September 2002 4:46 pm, you wrote:
>
>
> I took their advice, and used these /etc/fstab entries for my setup:
>
> darkforce:/home/darklord/tmp /home/jeremy/public nfs rw,hard,intr 0 0
> darkforce:/home/darklord/tmp /home/zerocool
On Monday 23 September 2002 11:40 pm, you wrote:
> twas as i was begining to expect, since i don't own server class kit, just
> old stuff i'm coopting - so i assume it will crash at some point:-), what
> would be better - intr or soft as an nfs mount option?
>
> bascule
Hi bascule. I just setup N
bascule <[EMAIL PROTECTED]> writes:
> 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 attac
twas as i was begining to expect, since i don't own server class kit, just
old stuff i'm coopting - so i assume it will crash at some point:-), what
would be better - intr or soft as an nfs mount option?
bascule
On Tuesday 24 September 2002 4:29 am, you wrote:
> bascule wrote on Tue, Sep 24, 2
bascule wrote on Tue, Sep 24, 2002 at 03:02:51AM +0100 :
> the process in question is:
> 040 500 32629 1 9 0 26112 10620 lock_p D ? 0:00 xmms
> the lock_p and D look interesting, xmms was playing files on an nfs share
That little D is what is killing you. When a hard nfs mo
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 o
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 intere
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
f
what do you do when 'kill -9 pid' doesn't work?
bascule
--
'You've got the loudest silences I ever did hear from anyone who wasn't dead!'
(Lords and Ladies)
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
