On Tuesday 10 February 2009 01:34:47 Arjan van der Oest wrote: > Hi Mel, > > Sorry for not getting back to you earlier, I have been out of the office > for some time... > > > Does this one also have a link UP message after nfs mounting? If not, > > then > > > there's your culprit: network isn't up at mountcritremote time. You > > should > > > mark it 'late' in fstab > > The UP message came more or less at the same time. Marking it late fixed > the problem, still leaving me puzzled why the NFS mounts work without > problem on identical machines but not in this one. Anyhow, since it's > not a critical fs, the late option works fine.
There's 2 scenarios for late NFS mounting: - local named: named gets started after mountcritremote, fixable with resolv.conf that has an additional nameserver or populate /etc/hosts. - slow network card and/or DHCP server causing the network card to be down or without IP address / invalid resolv.conf at mountcritremote. Not really fixable. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"