http://qa.mandrakesoft.com/show_bug.cgi?id=4268
------- Additional Comments From [EMAIL PROTECTED] 2003-06-09 14:27 ------- David Walser wrote: > autofs is a good way to go, but there is no bug here, and no intention of pushing anything. "pushing" ? I don't understand. There _is_ a bug here somewhere though... > mount -a doesn't mount any network mounts, that's not anything new. OK, but if you look at the hostory of this bug, it was suggested by Buchan Milne in the original response to this bug. > service netfs start does that (and it's a service you can enable to start on boot) OK, I checked netfs: chkconfig --list netfs netfs 0:off 1:off 2:off 3:on 4:on 5:on 6:off So it is running, but it doesn't mount NFS mounts at boot-time because of a race condition (eth0 is not up at the point where the service starts). This is made worse by the faster boot time of 2.6.x series kernels that I am using. Buchan Milne wrote: > And unfortunately, the whole point of ifplugd is to make DHCP > asynchronous (so you don't wait 30 secondds for a non-existent when you > are not connected). You can try not using ifplugd, by unchecking the > "network hotplugging" checkbox in drakconnect (or setting ' > MII_NOT_SUPPORTED=yes' in /etc/sysconfig/network-scripts/ifcfg-<interface> It strikes me that there is something not quite right with hotplug support then. Perhaps the NFS mounts should be mounted from hotplug when the interface comes up. -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------- Reminder: ------- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: The "netfs" init script runs before ifplugd called by the "network" initscript has brought up eth0. This causes NFS mounts to fail at startup time. They can be mounted manually after booting. ifplugd is correctly called with -w but this only makes it wait for a link beat. After detecting the link, it takes about 3 seconds for the interface to come up, and this is done asynchronuously, so the netfs script has already finished by that time.
