From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1GhSPB-0008Cg-Nr for garchives@archives.gentoo.org; Tue, 07 Nov 2006 14:58:26 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.8/8.13.8) with SMTP id kA7Eu5Wd028955; Tue, 7 Nov 2006 14:56:05 GMT Received: from alnrmhc14.comcast.net (alnrmhc14.comcast.net [206.18.177.54]) by robin.gentoo.org (8.13.8/8.13.8) with ESMTP id kA7Er4U1009056 for ; Tue, 7 Nov 2006 14:53:05 GMT Received: from [192.168.1.40] (c-69-141-3-197.hsd1.pa.comcast.net[69.141.3.197]) by comcast.net (alnrmhc14) with ESMTP id <20061107145259b1400cvir2e>; Tue, 7 Nov 2006 14:52:59 +0000 Message-ID: <45509DD7.7050404@paulscrap.com> Date: Tue, 07 Nov 2006 09:53:11 -0500 From: PaulNM User-Agent: Thunderbird 1.5.0.7 (X11/20060928) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] NTP: ntp-client doesn't start References: <455058C1.7010808@hawaiiantel.net> In-Reply-To: <455058C1.7010808@hawaiiantel.net> X-Enigmail-Version: 0.94.1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Archives-Salt: 821a993e-5b55-4aca-87c3-e3c474c1d42d X-Archives-Hash: 336cc4175ec0bc31e778ba43d320404d Christopher Kern wrote: > Hope this helps... > > > When investigating this myself, I found that I needed to set up a link > to the service in /etc/init.d with this command as the root user: > > "cd /etc/runlevels/default && ln -s /etc/init.d/ntp-client ." (no > quotes, of course) > > This works fine at boot, as the service start is indicated in the boot > display, and the time is indeed set to the correct time once executed > at boot time. I also found that one can alter the timeout for this > service by changing the NTPCLIENT_TIMEOUT variable in > /etc/conf.d/ntp-client file so that it is whatever you'd like it to > be. The default setting was 30 seconds, but I thought a shorter time > would have been better, especially at boot time. > > Contents of /etc/conf.d/ntp-client: > > # /etc/conf.d/ntp-client > Look here.. > # Command to run to set the clock initially ntp-client is meant to be a one time thing. > # Most people should just leave this line alone ... > # however, if you know what you're doing, and you > # want to use ntpd to set the clock, change this to 'ntpd' > NTPCLIENT_CMD="ntpdate" Ntpdate was a simple utility meant to be run as a cron job, but now is mostly depreciated in favor of using ntpd/openntpd. The full daemons are not the resource hogs they used to be, and are much better at handling clock skew. They keep track of the skew, so they only do a correction as often as needed. Using a daemon also helps keep the other ntp servers from getting pounded at certain points of the day by people who use cron jobs, which strains their resouces and makes it harder for you to get accurate info. You're a little better than most since you are doing daily syncs and not hourly or 4x a day, but do you have any idea how many people set up syncs at midnight? Use a daemon, it'll do a better job keeping your system in sync and be much nicer on all the ntp servers you're syncing against. OpenNTPD guide http://gentoo-wiki.com/HOWTO_NTP_Using_OpenNTPD NTPD guide http://gentoo-wiki.com/NTP PaulNM -- gentoo-user@gentoo.org mailing list