From owner-freebsd-questions@FreeBSD.ORG Fri Jul 22 16:44:07 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 26B4C16A421 for ; Fri, 22 Jul 2005 16:44:07 +0000 (GMT) (envelope-from list-freebsd-2004@morbius.sent.com) Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id AFC2E44428 for ; Fri, 22 Jul 2005 16:44:06 +0000 (GMT) (envelope-from list-freebsd-2004@morbius.sent.com) Received: from frontend2.messagingengine.com (frontend2.internal [10.202.2.151]) by frontend1.messagingengine.com (Postfix) with ESMTP id 4A380CC1ABE for ; Fri, 22 Jul 2005 12:44:05 -0400 (EDT) X-Sasl-enc: 4g23e/lsOLBk6y9Ct7JCA44CU0vl4AoPK+7JURJVrsvl 1122050642 Received: from gumby.localdomain (dsl-80-41-68-172.access.as9105.com [80.41.68.172]) by frontend2.messagingengine.com (Postfix) with ESMTP id EF64F56F785 for ; Fri, 22 Jul 2005 12:44:02 -0400 (EDT) From: RW To: freebsd-questions@freebsd.org Date: Fri, 22 Jul 2005 17:44:03 +0100 User-Agent: KMail/1.8.1 References: <20050722081554.U53583@malcolm.berkeley.edu> In-Reply-To: <20050722081554.U53583@malcolm.berkeley.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200507221744.03835.list-freebsd-2004@morbius.sent.com> Subject: Re: Possible problem with periodic daily processing 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: Fri, 22 Jul 2005 16:44:07 -0000 On Friday 22 July 2005 16:24, Mike Friedman wrote: > Because of clock drift on my system, I decided to run ntpdate daily, > instead of just at boot time. So, what I did was create a symlink in > /etc/periodic/daily: 600.ntpdate -> /etc/rc.d/ntpdate, thus leveraging > the existing ntpdate script that runs at boot time. My rc.conf already has > 'ntpdate_enable="YES"' and sets 'ntpdate_program' and 'ntpdate_hosts'. > In fact, if I cd to /etc/periodic/daily and manually enter './600.ntpdate > start', it runs fine. > > Yet, it appears that ntpdate is NOT running automatically each day as part > of periodic daily processing. Any ideas on why this is the case? Is > there a restriction about symlinks and periodic processing? That's not the best way to do it. Normally ntpdate corrects gross clock errors at boot time, and then ntpd keeps the clock on track by continuous adjustment. It's covered in the manual.