From owner-freebsd-questions@FreeBSD.ORG Mon Nov 7 09:20:33 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 17018106566B for ; Mon, 7 Nov 2011 09:20:33 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id C70948FC1C for ; Mon, 7 Nov 2011 09:20:32 +0000 (UTC) Received: by ggnk3 with SMTP id k3so4835370ggn.13 for ; Mon, 07 Nov 2011 01:20:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=z49SRfq4HuJix8vbJ3VV7aw/3poikH8fFkvPEHONGG0=; b=R5w1HDxDO0FzAedetQ6xVckrQb3Nuq8SoBr+68zmStkPB6A43AYt9PzegsU0ZHiZQ2 rwhHrq64RUPjNWGQrjoCIM1LfFQ2Jw4qE6JpNbjz/sInQZXBJTq3pfF/Am934/Oh3B+V ja/IRPcENfxGj25S7QFTbne0yaDJZkM02sZXQ= MIME-Version: 1.0 Received: by 10.236.180.101 with SMTP id i65mr33408657yhm.21.1320657632192; Mon, 07 Nov 2011 01:20:32 -0800 (PST) Received: by 10.236.95.45 with HTTP; Mon, 7 Nov 2011 01:20:31 -0800 (PST) In-Reply-To: References: Date: Mon, 7 Nov 2011 09:20:31 +0000 Message-ID: From: krad To: Robert Simmons Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-questions@freebsd.org Subject: Re: ntpdate on boot problem X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Nov 2011 09:20:33 -0000 On 6 November 2011 02:51, Robert Simmons wrote: > On Sat, Nov 5, 2011 at 7:43 PM, Warren Block 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