On Tue, 2012-01-10 at 23:57 +, Peter Humphrey wrote:
> On Tuesday 10 January 2012 21:45:21 Jeff Cranmer wrote:
>
>
>
> > Initially, the RTC options were not enabled in my kernel, but even
> after
>
> > setting these, I'm still getting this error. I'm adding all the
> device
>
> > drivers
Peter Humphrey wrote:
ls -d /dev/rt*
This is mine:
root@fireball / # ls -dl /dev/rt*
lrwxrwxrwx 1 root root 4 Jan 1 15:39 /dev/rtc -> rtc0
crw--- 1 root root 254, 0 Jan 1 15:39 /dev/rtc0
root@fireball / #
Mine links rtc to rtc0 which should work if the OP have the same.
Dale
:-)
On Tuesday 10 January 2012 21:45:21 Jeff Cranmer wrote:
> Initially, the RTC options were not enabled in my kernel, but even after
> setting these, I'm still getting this error. I'm adding all the device
> drivers as modules and trying again to see if I can remove this error.
> I suspect it is th
entoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] ntpd crashing
Date: Tue, 10 Jan 2012 22:42:07 +0100
On 10-Jan-12 22:18, Florian Philipp wrote:
>> Wouldn't it make more sense to get the clock set correctly on bootup
>> with ntpdate, and then have ntpd keep things in line moving f
Jeff Cranmer wrote:
On Tue, 2012-01-10 at 13:02 -0600, Dale wrote:
Florian Philipp wrote:
Besides, ntpd does not correct such large differences. It is not
designed to do this, especially on a running system. Activate
/etc/init.d/ntp-client. It will set the clock so that ntpd can keep it
in sync
Am 10.01.2012 22:42, schrieb Jarry:
> On 10-Jan-12 22:18, Florian Philipp wrote:
>
>>> Wouldn't it make more sense to get the clock set correctly on bootup
>>> with ntpdate, and then have ntpd keep things in line moving forward?
>>> Otherwise, every couple hours, you'd have your cron'd ntpddate ju
On Tue, 10 Jan 2012 15:59:45 -0500
Michael Mol wrote:
> > Servers with long uptimes should use ntpd, especially if it's apps
> > timestamp data.
> > Laptops and desktops should instead use ntpdate every one or few
> > hours, that is more suitable for those machines (usually they only
> > care abo
On Tue, 2012-01-10 at 13:02 -0600, Dale wrote:
> Florian Philipp wrote:
> > Besides, ntpd does not correct such large differences. It is not
> > designed to do this, especially on a running system. Activate
> > /etc/init.d/ntp-client. It will set the clock so that ntpd can keep it
> > in sync af
On 10-Jan-12 22:18, Florian Philipp wrote:
Wouldn't it make more sense to get the clock set correctly on bootup
with ntpdate, and then have ntpd keep things in line moving forward?
Otherwise, every couple hours, you'd have your cron'd ntpddate jumping
the clock around. I've had apps get stuck in
Am 10.01.2012 21:59, schrieb Michael Mol:
> Alan McKinnon wrote:
>> On Tue, 10 Jan 2012 13:02:38 -0600
>> Dale wrote:
>>
>>> Florian Philipp wrote:
Besides, ntpd does not correct such large differences. It is not
designed to do this, especially on a running system. Activate
/etc/i
Alan McKinnon wrote:
> On Tue, 10 Jan 2012 13:02:38 -0600
> Dale wrote:
>
>> Florian Philipp wrote:
>>> Besides, ntpd does not correct such large differences. It is not
>>> designed to do this, especially on a running system. Activate
>>> /etc/init.d/ntp-client. It will set the clock so that nt
On Tue, 10 Jan 2012 13:02:38 -0600
Dale wrote:
> Florian Philipp wrote:
> > Besides, ntpd does not correct such large differences. It is not
> > designed to do this, especially on a running system. Activate
> > /etc/init.d/ntp-client. It will set the clock so that ntpd can keep
> > it in sync a
Florian Philipp wrote:
Besides, ntpd does not correct such large differences. It is not
designed to do this, especially on a running system. Activate
/etc/init.d/ntp-client. It will set the clock so that ntpd can keep it
in sync afterwards. You can start ntp-client on a running system but
it m
Florian Philipp writes:
> Am 10.01.2012 18:43, schrieb Michael Mol:
> > Jeff Cranmer wrote:
> > Hm. That sounds like your tz (-0500) is being applied twice.
>
> Besides, ntpd does not correct such large differences. It is not
> designed to do this, especially on a running system. Activate
> /etc
Am 10.01.2012 18:43, schrieb Michael Mol:
> Jeff Cranmer wrote:
>> On Tue, 2012-01-10 at 13:56 +0800, W.Kenworthy wrote:
>>> Define crashing?
>>>
>>> This looks more like problems with yout TZ variables than ntpd.
>>>
>>> try "ntpq -p" to check if its actually running/locked. If ntpd is
>>> freewh
Jeff Cranmer wrote:
> On Tue, 2012-01-10 at 13:56 +0800, W.Kenworthy wrote:
>> Define crashing?
>>
>> This looks more like problems with yout TZ variables than ntpd.
>>
>> try "ntpq -p" to check if its actually running/locked. If ntpd is
>> freewheeling, it is prpbably because your time is too far
On Tue, 2012-01-10 at 13:56 +0800, W.Kenworthy wrote:
> Define crashing?
>
> This looks more like problems with yout TZ variables than ntpd.
>
> try "ntpq -p" to check if its actually running/locked. If ntpd is
> freewheeling, it is prpbably because your time is too far from lock so
> it will s
sts.gentoo.org
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] ntpd crashing
Date: Mon, 09 Jan 2012 16:25:39 -0500
Hi,
Can anyone give me any pointers as to how to diagnose a problem with
ntpd crashing. My time keeps defaulting to 5 hours earlier than it
should.
There's nothing in dmesg wh
Hi,
Can anyone give me any pointers as to how to diagnose a problem with
ntpd crashing. My time keeps defaulting to 5 hours earlier than it
should.
There's nothing in dmesg when I do dmesg | grep time, or dmesg | grep
ntp, but /etc/init.d/ntpd status tells me that ntpd has crashed.
Jeff
19 matches
Mail list logo
