On Sun, Oct 01, 2006 at 11:30:43PM -0400, Chaogui Zhang wrote: > > I won't be able to test if I can reproduce the problem (not deleting the > directory /var/run/network/mountnfs). Manual execution of the script > /etc/network/if-up.d/mountnfs now works perfectly. I will reboot the > system tomorrow when I get in my office and see if things will be > different at boot time (I doubt it).
Well, I was wrong. It was different. The script hangs at "mount -a -tnfs" After some testing, I think I figured out what went wrong and the errors are reproducible. At system boot time, when "ifup -a" is run, it brings up eth0 and then tries to execute /etc/network/if-up.d/mountnfs before eth0:0 is up. Well, in my case, the nfs directory is not accessible from eth0 but only from eth0:0, so the script hangs at "mount -a -tnfs". I worked around the problem by switching eth0 and eth0:0. Now everything works. BTW, the dangling /var/run/network/mountnfs was left behind because at some point I used "CTRL-C" to kill the hanging script and I didn't realize even the existence of the lock directory at that time. I don't know if there is a way to make the script wait until all interfaces are up and running. In any case, this issue needs to be resolved as on a multi-interface system, the script has no way of knowing which interface should be used to access the nfs directory. Best, Chaogui Zhang -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
