From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 39647138513 for ; Thu, 17 Jan 2013 15:35:42 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 03555E066B; Thu, 17 Jan 2013 15:35:33 +0000 (UTC) Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 94616E064A for ; Thu, 17 Jan 2013 15:35:31 +0000 (UTC) Received: from localhost (66-208-231-133.ubr01a.rte20201.pa.hfc.comcastbusiness.net [66.208.231.133]) by mrelay.perfora.net (node=mrus0) with ESMTP (Nemesis) id 0M2KJY-1T6NNN0hjo-00sHIK; Thu, 17 Jan 2013 10:35:30 -0500 Date: Thu, 17 Jan 2013 09:35:28 -0600 From: Bruce Hill To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] System won't boot if CMOS clock is slow Message-ID: <20130117153528.GH2656@server> References: 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 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Provags-ID: V02:K0:7saO91uYXFz6qxOWly+gRGd1Phyg3VAQTlERUqL+fZP yviGDfT+ezVEHbHQmwi7WGPyqI+EA9ThJ+iUpqIpK5JnUxR0sN NNHGkwdnHwFZfGgvwqwAix3I+Xhze6yjDmMOulQu41B7mLhs0q RDMeMYUYkLgO1KmlubgFQdIrdYeorMTQkzmgn3pO21rxTLnKKK C70r6Oj6yrbVAmBKDQQVHCU+hxx/CuGP/hSJ9UjxnC3pHZL6xn cS1UGoeE5/26QSSY+m8dzCq9+ykBELvi7UavCWadXSBS/4ZraV GKlaHjArsS9cwkKyiMpbaeVKmM2WrD4/p6dqDpyMZ97y5zxqw2 LIJvGVWK1iMx8aKoZC1Y= X-Archives-Salt: 7750fd7b-48b9-419e-9faf-c7d7c57712ab X-Archives-Hash: ff7ce55f6039705580637ce2f959e340 On Thu, Jan 17, 2013 at 03:06:23PM +0000, Stroller wrote: > > On 16 January 2013, at 16:43, Grant Edwards wrote: > > > I'm having problems with one of my Gentoo systems who's motherboard > > clock is a little slow. When the system comes up, the system time is > > set from the motherboard clock. If that's slow, something in the init > > system seems to panic because some file or other has a timestamp in > > the future. > > You've had lots of other suggestions here, but I think this is handled fine if you add ntp to the default runlevel (and assuming the system can connect to the net). The service would be ntpd (daemon) or ntp-client (client), but not ntp. Still you should change your CMOS battery. ;) -- Happy Penguin Computers >') 126 Fenco Drive ( \ Tupelo, MS 38801 ^^ support@happypenguincomputers.com 662-269-2706 662-205-6424 http://happypenguincomputers.com/ Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting