On Wed, Sep 12, 2012 at 2:59 PM, mike cloaked wrote:
> On Wed, Sep 12, 2012 at 1:02 PM, Stephen E. Baker
> wrote:
>
>> I think the usual response is, anyone can edit the wiki - please add what
>> you
>> think is needed.
>
> Point taken - I will try find some time to do that!
>
I edited the wiki
On Wed, Sep 12, 2012 at 1:02 PM, Stephen E. Baker
wrote:
> I think the usual response is, anyone can edit the wiki - please add what
> you
> think is needed.
Point taken - I will try find some time to do that!
--
mike c
On 11/09/2012 5:22 PM, mike cloaked wrote:
On Tue, Sep 11, 2012 at 8:06 PM, mike cloaked wrote:
On Tue, Sep 11, 2012 at 7:51 PM, Jan Steffens wrote:
On Tue, Sep 11, 2012 at 8:27 PM, Thomas Bächler wrote:
2) When chrony is not running, systemd-timedated runs periodically to
adjust the hardwa
On Tue, Sep 11, 2012 at 8:06 PM, mike cloaked wrote:
> On Tue, Sep 11, 2012 at 7:51 PM, Jan Steffens wrote:
>> On Tue, Sep 11, 2012 at 8:27 PM, Thomas Bächler wrote:
>>> 2) When chrony is not running, systemd-timedated runs periodically to
>>> adjust the hardware clock for drift (AFAIK, not sure
On Tue, Sep 11, 2012 at 7:51 PM, Jan Steffens wrote:
> On Tue, Sep 11, 2012 at 8:27 PM, Thomas Bächler wrote:
>> 2) When chrony is not running, systemd-timedated runs periodically to
>> adjust the hardware clock for drift (AFAIK, not sure that is the job
>> that timedated does).
>
> No. When chro
Am 11.09.2012 20:51, schrieb Jan Steffens:
> On Tue, Sep 11, 2012 at 8:27 PM, Thomas Bächler wrote:
>> 2) When chrony is not running, systemd-timedated runs periodically to
>> adjust the hardware clock for drift (AFAIK, not sure that is the job
>> that timedated does).
>
> No. When chrony isn't r
On Tue, Sep 11, 2012 at 8:27 PM, Thomas Bächler wrote:
> 2) When chrony is not running, systemd-timedated runs periodically to
> adjust the hardware clock for drift (AFAIK, not sure that is the job
> that timedated does).
No. When chrony isn't running, the hwclock isn't getting adjusted at
all. T
Am 11.09.2012 20:16, schrieb mike cloaked:
> However a question is where does the hardware clock get
> re-synchronised if it drifts out of time over a period unless it is
> occasionally resynchronised?
Three things:
1) On boot, the hardware clock is copied to the system clock. The
adjtime file sa
On Tue, Sep 11, 2012 at 7:15 PM, Thomas Bächler wrote:
>> OK I will try with chrony stopped - the first line of adjtime is:
>>
>> 0.00 0 0.00
>>
>> I saved the file as .bak before fiddling!
>
> Okay, that means your problem is NOT a broken adjtime. This basically
> says that your hardware
On Tue, Sep 11, 2012 at 5:52 PM, Thomas Bächler wrote:
> I guess you need to stop chrony when playing with hwclock. Maybe it is
> enough to just delete adjtime without that command.
>
> Forgot to tell you (but it's probably too late now) to post the first
> line of your /etc/adjtime, this would h
Am 11.09.2012 19:03, schrieb mike cloaked:
> On Tue, Sep 11, 2012 at 5:52 PM, Thomas Bächler wrote:
>> Am 11.09.2012 18:17, schrieb mike cloaked:
>
>> I guess you need to stop chrony when playing with hwclock. Maybe it is
>> enough to just delete adjtime without that command.
>>
>> Forgot to tell
On Tue, Sep 11, 2012 at 5:52 PM, Thomas Bächler wrote:
> Am 11.09.2012 18:17, schrieb mike cloaked:
> I guess you need to stop chrony when playing with hwclock. Maybe it is
> enough to just delete adjtime without that command.
>
> Forgot to tell you (but it's probably too late now) to post the fi
Am 11.09.2012 18:17, schrieb mike cloaked:
> On Tue, Sep 11, 2012 at 5:16 PM, mike cloaked wrote:
>> On Tue, Sep 11, 2012 at 11:59 AM, Thomas Bächler
>> wrote:
>>
>>> Your /etc/adjtime probably contains a faulty adjustment value. Delete
>>> it, hwclock --systohc, then reboot.
>>>
>> There is a p
On Tue, Sep 11, 2012 at 5:16 PM, mike cloaked wrote:
> On Tue, Sep 11, 2012 at 11:59 AM, Thomas Bächler wrote:
>
>> Your /etc/adjtime probably contains a faulty adjustment value. Delete
>> it, hwclock --systohc, then reboot.
>>
> There is a problem running the hwclock command:
>
> [root@lapmike3
On Tue, Sep 11, 2012 at 11:59 AM, Thomas Bächler wrote:
> Your /etc/adjtime probably contains a faulty adjustment value. Delete
> it, hwclock --systohc, then reboot.
>
There is a problem running the hwclock command:
[root@lapmike3 etc]# hwclock --systohc
hwclock: Cannot access the Hardware Clock
On Tue, Sep 11, 2012 at 11:59 AM, Thomas Bächler wrote:
> Does chrony install a .list file to /usr/lib/systemd/ntp-units.d?
>
[mike@lapmike3 Documents]$ cat /usr/lib/systemd/ntp-units.d/chrony.list
chrony.service
So yes this is the single line content of the chrony.list file
>> I would not mi
On Tue, Sep 11, 2012 at 11:59 AM, Thomas Bächler wrote:
> Am 11.09.2012 12:15, schrieb mike cloaked:
>> Recently I changed permanently to systemd - however I have noticed
>> that the system clock is out by some minutes just after I have booted
>> up and see for example:
>>
>> [mike@lapmike3 ~]$ ch
Am 11.09.2012 12:15, schrieb mike cloaked:
> Recently I changed permanently to systemd - however I have noticed
> that the system clock is out by some minutes just after I have booted
> up and see for example:
>
> [mike@lapmike3 ~]$ chronyc tracking
> Reference ID: 178.32.55.58 (gateway.omega.
On Tue, Sep 11, 2012 at 12:28:26PM +0200, Ralf Mardorf wrote:
> On Tue, 2012-09-11 at 11:15 +0100, mike cloaked wrote:
> > Recently I changed permanently to systemd - however I have noticed
> > that the system clock is out by some minutes just after I have booted
> > up and see for example:
> >
>
On Tue, 2012-09-11 at 11:15 +0100, mike cloaked wrote:
> Recently I changed permanently to systemd - however I have noticed
> that the system clock is out by some minutes just after I have booted
> up and see for example:
>
> [mike@lapmike3 ~]$ chronyc tracking
> Reference ID: 178.32.55.58 (ga
20 matches
Mail list logo
