On Sat, 2019-11-23 at 23:22 -0500, Sam Varshavchik wrote:
> Louis Lagendijk writes:
>
> > On Sat, 2019-11-23 at 10:09 -0500, Sam Varshavchik wrote:
> >
> > > So, hwclock must be getting synced. But I don't see where hwclock
> > > would be
> > > getting called from. grepping /lib/systemd/system fi
On Sun, 24 Nov 2019 15:24:16 +1030
Tim via users wrote:
> Some PCs don't keep time well, and that can account for one PC being
> different from the others, regardless of CMOS battery condition.
Amen :-). I've had at least one PC that would be off by about
a minute every hour if I had relied on th
On 2019-11-24 12:22, Sam Varshavchik wrote:
> Louis Lagendijk writes:
>
>> On Sat, 2019-11-23 at 10:09 -0500, Sam Varshavchik wrote:
>>
>> > So, hwclock must be getting synced. But I don't see where hwclock
>> > would be
>> > getting called from. grepping /lib/systemd/system finds nothing.
>> > hwc
On Sat, 2019-11-23 at 08:59 -0500, Sam Varshavchik wrote:
> I have chrony running and pointing to my ISP's time server, not the
> Fedora pool, so it's always the same NTP server.
>
> This box is up 24/7, and I just rebooted it. And I get this, after a
> reboot:
>
> Nov 23 08:53:10 shorty chronyd[
Louis Lagendijk writes:
On Sat, 2019-11-23 at 10:09 -0500, Sam Varshavchik wrote:
> So, hwclock must be getting synced. But I don't see where hwclock
> would be
> getting called from. grepping /lib/systemd/system finds nothing.
> hwclock
> itself comes from util-linux, which doesn't install any
On 2019-11-23 21:59, Sam Varshavchik wrote:
> Anyone know where to investigate this further?
Suggest you keep an eye on the drift by doing something like
date +%Y-%m-%d\ %H:%M:%S.%N > tdiff ; hwclock -r >> tdiff
on a periodic basis.
I would think it would be a good idea to do it just before a
On Sat, 2019-11-23 at 10:09 -0500, Sam Varshavchik wrote:
> Tom Horsley writes:
>
> > On Sat, 23 Nov 2019 08:59:02 -0500
> > Sam Varshavchik wrote:
> >
> > > Anyone know where to investigate this further?
> >
> > The linux app that syncs to the hardware is "hwclock" (which
> > has various obscur
Tom Horsley writes:
On Sat, 23 Nov 2019 08:59:02 -0500
Sam Varshavchik wrote:
> Anyone know where to investigate this further?
The linux app that syncs to the hardware is "hwclock" (which
has various obscure parameters described in the man page).
You could make a script to sync with hwclock t
On 2019-11-23 22:33, Ed Greshko wrote:
> Maybe add an ExecStop=
Sorry, that should have been ExecStopPost=
--
The key to getting good answers is to ask good questions.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email
CMOs battery on the motherboard?
> On 23 Nov 2019, at 14:00, Sam Varshavchik wrote:
>
> I have chrony running and pointing to my ISP's time server, not the Fedora
> pool, so it's always the same NTP server.
>
> This box is up 24/7, and I just rebooted it. And I get this, after a reboot:
>
>
On 2019-11-23 22:22, Tom Horsley wrote:
> On Sat, 23 Nov 2019 08:59:02 -0500
> Sam Varshavchik wrote:
>
>> Anyone know where to investigate this further?
> The linux app that syncs to the hardware is "hwclock" (which
> has various obscure parameters described in the man page).
>
> You could make a
On Sat, 23 Nov 2019 08:59:02 -0500
Sam Varshavchik wrote:
> Anyone know where to investigate this further?
The linux app that syncs to the hardware is "hwclock" (which
has various obscure parameters described in the man page).
You could make a script to sync with hwclock then reboot
and see if t
I have chrony running and pointing to my ISP's time server, not the Fedora
pool, so it's always the same NTP server.
This box is up 24/7, and I just rebooted it. And I get this, after a reboot:
Nov 23 08:53:10 shorty chronyd[992]: System clock TAI offset set to 37 seconds
Nov 23 08:53:10 short
13 matches
Mail list logo
