Date: Mon, 7 Nov 2011 09:20:31 +0000 From: krad <kraduk@gmail.com> To: Robert Simmons <rsimmons0@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: ntpdate on boot problem Message-ID: <CALfReycpJ8mP9-_WJeymPe-QEznPozMr_chVwgs3R96MT1Hyzg@mail.gmail.com> In-Reply-To: <CA%2BQLa9A4e0LxoHD1gOT47iwwymVoT8t5-S5d2B8TGyB4uytzfQ@mail.gmail.com> References: <CA%2BQLa9CfBYRshynTPDkYDapA_M_rDr-UD6sh-JYBGfSPONBJYQ@mail.gmail.com> <alpine.BSF.2.00.1111051653120.28513@wonkity.com> <CA%2BQLa9A4h-jK421pgPxe0wDZCnFnN2LV0N6YFQ32YWqbOw2LKg@mail.gmail.com> <alpine.BSF.2.00.1111051739330.28513@wonkity.com> <CA%2BQLa9A4e0LxoHD1gOT47iwwymVoT8t5-S5d2B8TGyB4uytzfQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 6 November 2011 02:51, Robert Simmons <rsimmons0@gmail.com> wrote: > On Sat, Nov 5, 2011 at 7:43 PM, Warren Block <wblock@wonkity.com> wrote: > > netwait_enable="YES" > > netwait_ip="192.168.1.1" # IP address to ping to verify network is up > > netwait_if="em0" # interface to use > > > > > > Also there's netwait_timeout, which defaults to 60 in > /etc/defaults/rc.conf. > > I've finally got a combination of suggested configurations that get me > to where I want to be (using ntpd, ntpdate, and netwait). > > However, I've found that I still need ntpdate_enable="YES" rather than > ntpd_sync_on_start="YES". The reason for this is that I'm running at > securelevel 3, and ntpd takes too long to get up, running, and sync > the clock. By the time it tries to adjust the clock, secure level has > already been raised preventing the adjustment. > > Is there a way to make securelevel wait until ntpd has made its > adjustments? When I use ntpdate at this point, it seems like the init > scripts are sequential, and it waits until ntpdate is done before > continuing and later raising securelevel. > > It seems that even though ntpdate is deprecated that it is still > required if you want to run securelevel 3. > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " > freebsd-questions-unsubscribe@freebsd.org" > Another thing you may want to look at is your switchport config (assuming its managed), if you are running STP it can take upto a minute for the port to go into forwarding state after the line is up. You can do two things to get around this. 1. use rstp instead - this is the better safer way forward. However you may not have control of the network and could be a big thing to do depending on your organization. 2. enable portfast on the relevant switches. This is potentially dangerous as it disables stp and therefore potentially exposes you to switching loops. However if the port is only ever plugged into on machine and EU dont play with the cables shold be fine
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CALfReycpJ8mP9-_WJeymPe-QEznPozMr_chVwgs3R96MT1Hyzg>