problem with network initialization in SuSE 10???
Hi, Okay folks! Please help, this is driving me nuts. Apologies for the X-posting. I have a AMD64 machine (SuSE 10 64bit) connected to a switch. At boot time my PC tries to NFS mount 3 exported partitions from a SLES server attached to the same switch. The PC fails to mount any of the NFS shares at boot time. 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. So, I inserted a `sleep 20` prior to the ping command, the machine sits there, then reports "no route to host". Eventually, the network must come up, since if I then log in through KDM I can browse the web etc. 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? FYI we have several x86 machines and a single AMD64 (SuSE 9.3 64bit) that start up and NFS with the server with no problems. As always, any help much appreciated. Cheers, Jon.
participants (1)
-
Jonathan Brooks