Sujet : Re: GNU/Linux System Clock Drift
De : sc (at) *nospam* fiat-linux.fr (Stéphane CARPENTIER)
Groupes : comp.os.linux.advocacyDate : 09. May 2025, 22:19:57
Autres entêtes
Organisation : Mulots' Killer
Message-ID : <681e717d$0$29733$426a34cc@news.free.fr>
References : 1
User-Agent : slrn/pre1.0.4-9 (Linux)
Le 08-05-2025, Farley Flud <
ff@linux.rocks> a écrit :
How much does your system clock (not hardware clock) drift?
For my hardware, don't know and I don't care. For my system: it doesn't
drift. The ntp is there to prevent it. And it works fine out of the box.
I boot my GNU/Linux machines regularly and at each boot I set
the system clock (and also the hardware clock) from the time
servers at NIST using openrdate:
>
https://github.com/resurrecting-open-source-projects/openrdate
>
Openrdate will report a drift of about 0.7 seconds per day for all
of my machines.
All of your machines drift at the same level? It's hard to believe. It
mostly look like you made up the value.
How much does your system clock drift?
I told you: it doesn't. Even my watch, not connected to Internet,
doesn't drift as much as your machines. You should learn how to manage
your system properly.
Of course, using a standalone desktop workstation, such drift
is of no consequence. I could set the system clock far more
frequently but what the fuck for?
If you don't care, why do you bring the subject?
How much does your system clock drift?
For the third time, my system doesn't drift. Why do you ask the same
question three time if it's of no consequence?
Can the distro lackeys even know?
Of course I know. And a default ntp configuration of any distro lackey
works more properly than your computers. You should remember the simple
sentence: "if it ain't broke, don't fix it."
-- Si vous avez du temps à perdre :https://scarpet42.gitlab.io