| From | Sent On | Attachments |
|---|
| Subject: | NFS server not responding prevents boot | |
|---|---|---|
| From: | Steven Hartland (kill...@multiplay.co.uk) | |
| Date: | May 19, 2006 12:47:24 am | |
| List: | org.freebsd.freebsd-hackers | |
Refine Search
| From | Sent On | Attachments |
|---|---|---|
| Steven Hartland | May 19, 2006 12:37 am | |
| Steven Hartland | May 19, 2006 12:47 am | |
| Mike Meyer | May 19, 2006 2:33 am | |
| Sergey Babkin | May 19, 2006 11:30 am | |
| Steven Hartland | May 19, 2006 1:17 pm | |
| Chuck Lever | May 19, 2006 2:04 pm | |
| Kip Macy | May 20, 2006 7:57 pm |
| Subject: | NFS server not responding prevents boot | |
|---|---|---|
| From: | Steven Hartland (kill...@multiplay.co.uk) | |
| Date: | May 19, 2006 12:47:24 am | |
| List: | org.freebsd.freebsd-hackers | |
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 the man pages.
The option for anyone interested is "bg" for -b from the command line to mount: [quote="man mount_nfs"] -b If an initial attempt to contact the server fails, fork off a child to keep trying the mount in the background. Useful for fstab(5), where the file system mount is not critical to multi- user operation. ... bg Same as -b. [/quote]
Steve
================================================
This e.mail is private and confidential between Multiplay (UK) Ltd. and the
person or entity to whom it is addressed. In the event of misdirection, the
recipient is prohibited from using, copying, printing or otherwise disseminating
it or any information contained in it.
In the event of misdirection, illegible or incomplete transmission please
telephone (023) 8024 3137
or return the E.mail to post...@multiplay.co.uk.

