On Sat, 6 Sep 2003, [luigiwalser] wrote:
> http://qa.mandrakesoft.com/show_bug.cgi?id=4268
> ------- Additional Comments From [EMAIL PROTECTED] 2003-06-09 14:10 -------
> autofs is a good way to go, but there is no bug here, and no intention
> of pushing anything.
>
> mount -a doesn't mount any network mounts, that's not anything new.
I am quite sure it used to, as our internal config rpm used to have this
(before we published automount entries in LDAP), just after adding
configurations for our NFS shares:
echo "Mounting nfs shares:"
mount -a
This package was used up until just after the release of 9.1, and I am
sure it worked ...
> service netfs start does that (and it's a service you can enable to
> start on boot)>
Well, this returns us to the original bug report, which is that netfs is
started too soon after network, and ifplugd may not have waited long
enough to guarantee the network is up before netfs starts.
I haven't seen this myself, but maybe our DHCP server is faster, or my
machine is slower, or it appeared after we switched to using autofs.
Maybe a hack for the moment is to have a configurable pause for ifplugd?
Or maybe netfs needs to be moved to behind something else that is
guaranteed to wait long enough for the network?
Regards,
Buchan
--
|----------------Registered Linux User #182071-----------------|
Buchan Milne Mechanical Engineer, Network Manager
Cellphone * Work +27 82 472 2231 * +27 21 8828820x121
Stellenbosch Automotive Engineering http://www.cae.co.za
GPG Key http://ranger.dnsalias.com/bgmilne.asc
1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7
*****************************************************************
Please click on http://www.cae.co.za/disclaimer.htm to read our
e-mail disclaimer or send an e-mail to [EMAIL PROTECTED] for a copy.
*****************************************************************
