Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 5 Nov 2011 17:52:22 -0600 (MDT)
From:      Warren Block <wblock@wonkity.com>
To:        freebsd-questions@freebsd.org
Subject:   Re: ntpdate on boot problem
Message-ID:  <alpine.BSF.2.00.1111051743180.28513@wonkity.com>
In-Reply-To: <alpine.BSF.2.00.1111051908410.91432@fledge.watson.org>
References:  <CA%2BQLa9CfBYRshynTPDkYDapA_M_rDr-UD6sh-JYBGfSPONBJYQ@mail.gmail.com> <alpine.BSF.2.00.1111051653120.28513@wonkity.com> <alpine.BSF.2.00.1111051908410.91432@fledge.watson.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 5 Nov 2011, doug@safeport.com wrote:

> On Sat, 5 Nov 2011, Warren Block wrote:
>> On Sat, 5 Nov 2011, Robert Simmons wrote:
>> 
>>> I've had this problem with machines using DHCP and the solution was to
>>> use SYNCDHCP rather than DHCP in rc.conf.  However, this box is using
>>> a static IP address.  But the problem seems to be similar.
>> 
>> Yes, it is.  FreeBSD 8-STABLE and 9 have /etc/rc.d/netwait just for this.
>
> I do not see this in the handbook. Did I just miss it?. IMO the necessary 
> synchronization should just be built in to booting.

AFAIK it's not in the Handbook yet.  The problem is that some network 
interfaces actually take a while to come up after ifconfig is done 
setting them up.  The amount of time taken could depend on the local 
network with autonegotiation and such.

Another approach is to set up the DHCP server--if there is one--to 
assign static addresses based on MAC address.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1111051743180.28513>