Date: Tue, 25 Oct 2011 00:36:56 +0100 From: "Steven Hartland" <killing@multiplay.co.uk> To: "Jeremy Chadwick" <freebsd@jdc.parodius.com>, "Miroslav Lachman" <000.fbsd@quip.cz> Cc: freebsd-stable@freebsd.org Subject: Re: ntpd couldn't resolve host name on system boot Message-ID: <B26B1B7BC38B4479B103B78B2175234D@multiplay.co.uk> References: <4EA5EBB5.3090101@quip.cz> <20111024232750.GA74032@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
----- Original Message -----
From: "Jeremy Chadwick" <freebsd@jdc.parodius.com>
> The problem is that the networking layer is not TRULY available by the
> time ntpd starts. This does have to do with NIC drivers, but the same
> behaviour can be seen on all NICs, including excellent ones like em(4).
This is generally caused by links to high end switches e.g. cisco which
havent had their "server" ports configured with portfast or similar
settings. This creates quite a delay once link establishes before traffic
is passed and hence the issue.
netwait is an excellent script which fixes this and other network dependency
issues, something we use as standard on all our machines now :)
Regards
Steve
================================================
This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it.
In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337
or return the E.mail to postmaster@multiplay.co.uk.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B26B1B7BC38B4479B103B78B2175234D>