Um that is what intr is for - and it won't cause silent data loss.
-Kip
On 5/19/06, Sergey Babkin <[EMAIL PROTECTED]> wrote:
>From: Steven Hartland <[EMAIL PROTECTED]>
>> Anyway the big question is how can I change all our NFS
>> mounts so that failed mounts dont prevent the machines
>> bo
Sergey Babkin wrote:
From: Steven Hartland <[EMAIL PROTECTED]>
Anyway the big question is how can I change all our NFS
mounts so that failed mounts dont prevent the machines
booting to the point where they can be fixed remotely
i.e. have started sshd.
Doh!! spent ages googling for the answer
Sergey Babkin wrote:
I usually use "soft,bg". The "soft" option makes the
operations on this filesystem fail if the server
is not available instead of hanging (unkillable!)
forever and waiting for the server to come up.
Good tip thanks!
Steve
==
>From: Steven Hartland <[EMAIL PROTECTED]>
>> Anyway the big question is how can I change all our NFS
>> mounts so that failed mounts dont prevent the machines
>> booting to the point where they can be fixed remotely
>> i.e. have started sshd.
>
>Doh!! spent ages googling for the answer then found
In <[EMAIL PROTECTED]>, Steven Hartland <[EMAIL PROTECTED]> typed:
> I was doing some kernel patches the other day and rebooted
> a FreeBSD 5.4 machine to pick them up, unfortunately I didn't
> notice someone had put in a bad nfs mount in /etc/fstab
> i.e. to a machine that no longer existed.
>
>
Steven Hartland wrote:
Anyway the big question is how can I change all our NFS
mounts so that failed mounts dont prevent the machines
booting to the point where they can be fixed remotely
i.e. have started sshd.
Doh!! spent ages googling for the answer then found it
in 2mins of looking through
6 matches
Mail list logo
