NFS mount not automount at boot time
Hello, I have setup an NFS mount to be automatically mounted at boot-time, but it doesn't happen. It just simply isn't mounted after booting. mount -a will immediately a quickly mount the directory, as will a manual mount command called by the user or root. The fact that mount -a works greatly confuses me. Here's the fstab entry: 192.168.0.205:/home/orderclient/orderentry /home/orderclient/orderentry nfs auto,rw,hard,intr,rsize=8192,wsize=8192,nolock,user 0 0 (All one lines - email line wrapping is interfering here of course). On the server side: /home/orderclient/orderentry 192.168.0.0/255.255.255.0 (rw,async,anonuid=1000,anongid=100) (again, all one line) Any ideas what's preventing this from auto mounting at startup? Thanks. -- ---------------------------------------------------- Jonathan Wilson Cedar Creek Software http://www.cedarcreeksoftware.com
Hi JW! hmmm, chkconfig nfs and chkconfig nfslock both report on? -- michael On Fri, 20 Aug 2004, JW wrote:
Hello,
I have setup an NFS mount to be automatically mounted at boot-time, but it doesn't happen. It just simply isn't mounted after booting.
MG >Hi JW! MG > MG >hmmm, chkconfig nfs and chkconfig nfslock both report on? On the client? No. I insserved them and that seems to have solved the problem. Sorry, I don't recall having to do that before. Thanks. -- ---------------------------------------------------- Jonathan Wilson Cedar Creek Software http://www.cedarcreeksoftware.com
On Friday 20 Aug 2004 19:14 pm, JW wrote:
Hello,
I have setup an NFS mount to be automatically mounted at boot-time, but it doesn't happen. It just simply isn't mounted after booting.
mount -a will immediately a quickly mount the directory, as will a manual mount command called by the user or root.
The fact that mount -a works greatly confuses me.
Here's the fstab entry:
192.168.0.205:/home/orderclient/orderentry /home/orderclient/orderentry nfs auto,rw,hard,intr,rsize=8192,wsize=8192,nolock,user 0 0
(All one lines - email line wrapping is interfering here of course).
On the server side:
/home/orderclient/orderentry 192.168.0.0/255.255.255.0 (rw,async,anonuid=1000,anongid=100)
That all looks fine - have a look at lines 40 - 55 of /etc/init.d/nfs - it suggests a possible solution. HTH Dylan -- "I see your Schwartz is as big as mine" -Dark Helmet
participants (3)
-
Dylan
-
JW
-
Michael Galloway