On Monday 06 February 2006 13:43, Jonathan Brooks wrote:
I suspect that there could be a couple of things broken, since if I insert a ping command at the end of the start) section of etc/init.d/network, my machine reports "no route to host". Leading me to think that the network really isn't up.
It's probably some problem talking to the switch. Double check the cabling and the switch configuration.
But the only way I _ever_ get my NFS shares mounted is if I issue a `mount -vat nfs` command manually.
Now I don't mind waiting for the network to come up, but shouldn't SuSE be waiting too? I.e. what's the point in trying to mount NFS shares if you don't have a working network?
You could file an enhancement bug in bugzilla.novell.com. But i wouldn't hold my breadth of that it gets fixed because it's a nasty problem and making things synchronous at boot time has a couple of drawbacks (for once it's slower). Better you just use autofs instead. In general putting NFS mounts into fstabs is fragile and not really good practice and automounters are designed to deal with all these problems. I remember long ago seeing a cluster of machines that had circular dependencies in their boot time NFS mounts. Generated quite a mess when the cluster had to be rebooted. -Andi