On 2015-07-03 15:38:02 +0200, Michael Biebl wrote:
> In short, your ntp client should ensure that the clock is synced to RTC
> (google for "ntp 11 min mode sync" if you want to know more). For that
> we enable timesyncd by default in systemd.
Thanks for the information, but the documentation shoul
On Friday 03 July 2015 14:38:02 Michael Biebl wrote:
> Am 03.07.2015 um 15:18 schrieb Arno Schuring:
> >> Date: Fri, 3 Jul 2015 15:07:34 +0200
> >> From: vinc...@vinc17.net
> >>
> >> When I run "hwclock --systohc" manually before the reboot, the clock
> >> is OK after reboot. So, this seems to be a
> Date: Fri, 3 Jul 2015 15:38:02 +0200
> From: bi...@debian.org
>
> Am 03.07.2015 um 15:18 schrieb Arno Schuring:
>>
>>> Date: Fri, 3 Jul 2015 15:07:34 +0200
>>> From: vinc...@vinc17.net
>>>
>>> When I run "hwclock --systohc" manually before the reboot, the clock
>>> is OK after reboot. So, this
Am 03.07.2015 um 15:18 schrieb Arno Schuring:
>
>> Date: Fri, 3 Jul 2015 15:07:34 +0200
>> From: vinc...@vinc17.net
>>
>> When I run "hwclock --systohc" manually before the reboot, the clock
>> is OK after reboot. So, this seems to be a systemd bug. I've reported:
>>
>> https://bugs.debian.org/cgi
On Friday 03 July 2015 14:18:50 Arno Schuring wrote:
> > Date: Fri, 3 Jul 2015 15:07:34 +0200
> > From: vinc...@vinc17.net
> >
> > When I run "hwclock --systohc" manually before the reboot, the clock
> > is OK after reboot. So, this seems to be a systemd bug. I've reported:
> >
> > https://bugs.deb
> Date: Fri, 3 Jul 2015 15:07:34 +0200
> From: vinc...@vinc17.net
>
> When I run "hwclock --systohc" manually before the reboot, the clock
> is OK after reboot. So, this seems to be a systemd bug. I've reported:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790974
Michael, since I've seen
On 2015-07-01 02:24:14 +0200, Vincent Lefevre wrote:
> On 2015-06-30 18:15:18 -0400, Gary Dale wrote:
> > Is your cmos battery still providing power?
>
> The machine is new, so it should. The machine was also constantly on
> AC power.
>
> > Either that or your hardware clock could be broken or ve
On 2015-06-30 18:15:18 -0400, Gary Dale wrote:
> Is your cmos battery still providing power?
The machine is new, so it should. The machine was also constantly on
AC power.
> Either that or your hardware clock could be broken or very
> inaccurate.
If it loses 15 seconds just the time of a reboot,
On 30/06/15 05:52 PM, Vincent Lefevre wrote:
I've noticed that with my new HP ZBook G2, the clock loses time after
a reboot. Below is the openntpd log without the "peer" messages ("ntp
engine ready" means that this is just after a reboot). What is the
cause? Which part of the software is responsi
I've noticed that with my new HP ZBook G2, the clock loses time after
a reboot. Below is the openntpd log without the "peer" messages ("ntp
engine ready" means that this is just after a reboot). What is the
cause? Which part of the software is responsible to sync the RTC?
Jun 29 17:25:43 zira ntpd
on Sun, Mar 17, 2002, Greg Murphy ([EMAIL PROTECTED]) wrote:
> Greetings,
>
> My computer for some reason seems to be losing time at a rate of about 20
> minutes per 10-15 hours. I was under the impression that linux keeps track of
In addition to the hwclock adjustments, you
On Mon, 2002-03-18 at 06:05, Greg Murphy wrote:
> Greetings,
>
> My computer for some reason seems to be losing time at a rate of about 20
> minutes per 10-15 hours. I was under the impression that linux keeps track of
> the time from clock cycles. I have not rebooted my machin
On Sun, Mar 17, 2002 at 04:05:55PM -0600, Greg Murphy wrote:
> Greetings,
>
> My computer for some reason seems to be losing time at a rate of about 20
> minutes per 10-15 hours. I was under the impression that linux keeps track of
> the time from clock cycles. I have not reboote
On Sun, Mar 17, 2002 at 11:03:17PM -0500, Jerome Acks Jr wrote:
> I have no idea about why your computer would be losing time. You could set up
> a
> Network Time Protocol daemon (for example: nptd) to syncronize your clock
> with internet time servers. You probably have to rese
On Sun, Mar 17, 2002 at 04:05:55PM -0600, Greg Murphy wrote:
> Greetings,
>
> My computer for some reason seems to be losing time at a rate of about 20
> minutes per 10-15 hours. I was under the impression that linux keeps track of
> the time from clock cycles. I have not reboote
On Sun, Mar 17, 2002 at 16:05, Greg Murphy wrote:
> My computer for some reason seems to be losing time at a rate of about 20
> minutes per 10-15 hours. I was under the impression that linux keeps track of
> the time from clock cycles. I have not rebooted my machine in a week, so i
Greetings,
My computer for some reason seems to be losing time at a rate of about 20
minutes per 10-15 hours. I was under the impression that linux keeps track of
the time from clock cycles. I have not rebooted my machine in a week, so if
that previous assumption is correct, then that would
Hello all,
Does noflushd affect uptime? I'm a little puzzeled as to why my
uptime says 2:16 when in fact the machine has been on for about 2
weeks.
Any insights?
Thanks,
Matt
Opps,
I figured it out. Turns out that I had a lousy
/etc/adjtime file. This file is used and set by "hwclock"
to track drift (inaccuracy) in the HW clock. Turns out
that I must have run "hwclock" twice in quick succession
durring a brief peroid of major drift in the clock.
"hwclock" assu
This is really odd.
I have a dual boot system. I set the time by doing:
rdate ; hwclock --settohc --utc
...where is one of the naval time servers. I've been
using ntp2.usno.navy.mil.
This seems to work fine.
rdate -p ; date
show the same time. the time is set in the CMOS clock.
I ch
20 matches
Mail list logo
