From owner-freebsd-questions@FreeBSD.ORG Sun Nov 6 02:51:17 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 4A4E3106564A for ; Sun, 6 Nov 2011 02:51:17 +0000 (UTC) (envelope-from rsimmons0@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id 0CC408FC15 for ; Sun, 6 Nov 2011 02:51:16 +0000 (UTC) Received: by mail-yw0-f54.google.com with SMTP id 32so5232648ywt.13 for ; Sat, 05 Nov 2011 19:51:16 -0700 (PDT) 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 :content-type; bh=wC75IC7IABU03Q3s4M2b5u3XJqoSpMycFk+PImI/RK8=; b=a53/71EWue4k0b4rE5sFSK3KcC7J11ki4D+nUE2OBAg2jeBH5NTqRzVZEnfA4DyUr8 MDHJHk921fc8QdpP0QsMw6b8h1bLGS+U9Eq+/Dk4Ig37BGLyFOa/NAPE8GF7UNKKHkSy +TiIQLN4EzygcrGEJJEGF7QY3ff5vDNz7wWqI= MIME-Version: 1.0 Received: by 10.182.69.52 with SMTP id b20mr5292653obu.58.1320547876465; Sat, 05 Nov 2011 19:51:16 -0700 (PDT) Received: by 10.182.44.34 with HTTP; Sat, 5 Nov 2011 19:51:16 -0700 (PDT) In-Reply-To: References: Date: Sat, 5 Nov 2011 22:51:16 -0400 Message-ID: From: Robert Simmons To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 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: Sun, 06 Nov 2011 02:51:17 -0000 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.