From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21621 invoked by uid 1002); 18 Mar 2003 13:25:44 -0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 11181 invoked from network); 18 Mar 2003 13:25:44 -0000 From: Dylan Carlson Reply-To: absinthe@gentoo.org To: Andy Arbon , gentoo-dev Date: Tue, 18 Mar 2003 08:25:42 -0500 User-Agent: KMail/1.5 References: <3E770D40.9050106@andrewarbon.co.uk> <200303181325.35251.gentoo-user@devrieze.net> <3E771BC9.7040604@andrewarbon.co.uk> In-Reply-To: <3E771BC9.7040604@andrewarbon.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200303180825.42859.absinthe@gentoo.org> Subject: Re: [gentoo-dev] ntpd and ntpdate X-Archives-Salt: 15e2e584-c08c-400f-9ace-dde2be67ee8c X-Archives-Hash: 390f151cfe2c3e147240c9288fd1c314 On Tuesday 18 March 2003 08:14 am, Andy Arbon wrote: > > Thanks for the advice. This still isn't really what I was after. I want > a really lightweight way of making sure that my machines are in > reasonable sync, but I'm not really worried about it enough to want to > have another daemon process hanging around looking after the time. Try merging net-misc/rdate, and just put rdate in your root crontab. rdate works fine if you don't need microsecond accuracy ... # rdate -s Also look into using 'hwclock --systohc' as well. The man pages have all the info you will need. Cheers, Dylan Carlson Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x708E165F Key fingerprint = 3AEA DE38 FE42 15A6 C0E2 730E 3D04 BCC1 708E 165F -- gentoo-dev@gentoo.org mailing list