From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1LUjVL-0007Un-Td for garchives@archives.gentoo.org; Wed, 04 Feb 2009 15:17:32 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 81BE0E05B7; Wed, 4 Feb 2009 13:57:19 +0000 (UTC) Received: from yx-out-1718.google.com (yx-out-1718.google.com [74.125.44.154]) by pigeon.gentoo.org (Postfix) with ESMTP id 55B82E05B7 for ; Wed, 4 Feb 2009 13:57:19 +0000 (UTC) Received: by yx-out-1718.google.com with SMTP id 4so957442yxp.46 for ; Wed, 04 Feb 2009 05:57:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=fe7ZJsAVW3LQet3l+eFz7XGvR3T+pf8lRbz8tIzWdJg=; b=lrJjN30WvbBWMipM5R6lWzlR1vPeeLCW/SU1IjsG0hiTv9ZZwQ/1LAkQtAI25ubMGN lY4lPHYiYv03vSswxJo1p64FhV8PlviOnIxkir0XPzjDzII3EoToeRoqEttaFrIYeqeK SOnUI6ECyLjHp9MVuveCereZ/e/qzj8VgT5AM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=WGguu3N97ZeMJ2FXtw90GAMPtuavxMDgKe42dqkVTqSYKDNksiAdrlKLXPgM95p9H3 wxXduTlHlRb9KfrZy0Zfcgi+VVZldrPTVNbn6rhxV2CijEVgtuHNm6Kom+/9obcwlIur V40S/yeP3hq50oXoIpdESIvQWqPayN37pJyK4= Received: by 10.90.65.5 with SMTP id n5mr637833aga.98.1233755823179; Wed, 04 Feb 2009 05:57:03 -0800 (PST) Received: from ?4.230.117.227? (dialup-4.230.117.227.Dial1.Houston1.Level3.net [4.230.117.227]) by mx.google.com with ESMTPS id 32sm11175404aga.5.2009.02.04.05.57.00 (version=SSLv3 cipher=RC4-MD5); Wed, 04 Feb 2009 05:57:02 -0800 (PST) Message-ID: <49899EAA.5060206@gmail.com> Date: Wed, 04 Feb 2009 07:56:58 -0600 From: Dale User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.19) Gecko/20081227 SeaMonkey/1.1.14 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] /etc/init.d/: ntpd or ntp-client? References: <43F46B7E-4EA3-471C-9C64-9A516B32FFE8@stellar.eclipse.co.uk> In-Reply-To: <43F46B7E-4EA3-471C-9C64-9A516B32FFE8@stellar.eclipse.co.uk> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Archives-Salt: e102beec-b08e-47a9-81f6-dcc17043a13b X-Archives-Hash: 7625e992ff5bf94c3c8e27213e073846 Stroller wrote: > Hi there, > > I just logged into one of my machines that has recently been powered > down for a few days - not a terribly common occurrence with my servers > - to find a date of January 30th showing. > > I used to run ntp-client, but AIUI adding this to the default runlevel > only sets the clock once at boot up. Of course the problem with that > is that the computer's clock can become inaccurate if the spring > tension is weak, as is obviously the case in my older PCs. > > So a while back I changed /etc/runlevels/default so that ntpd is > started instead. > > I understood that ntpd was not only a server for my LAN (a facility I > don't use) but that it would also periodically check the time with > upstream servers & keep the machine's clock in constant sync. > > So when I found the clock to be a week out of date I checked that ntpd > appeared to be running (it was) and restarted it. The date remained > the same. Stopping ntpd & starting ntp-client corrected the date > immediately. > > Before I do any investigation, can someone tell me if my understanding > so far is correct? Is ntpd supposed to keep the machine's clock in > constant sync, or is it only (say) a server to offer the date to > clients? (depending upon the clock being set correctly by other means) > I thought I had configured ntpd with upstream servers separately from > ntp-client. > > Stroller. > > I use ntpd here as well. Ntpd does not set it immediately like other commands do. From my understanding ntpd compares its time to a server then gradually adjusts the clock by speeding up or slowing down the clock. It takes a while to do this. If your clock is a long ways off then it will take longer. I'm not sure if this is still true but I read that if it is way off, several days or longer I would assume, it will require you to adjust it manually or you could set it with ntpdate which will set it instantly from one of the time servers. In this case, set the clock then restart ntpd. Hope that helps. Dale :-) :-)