Article View: pl.comp.os.linux
Article #908049Re: Synchronizacja czasu
From: marrgol
Date: Mon, 10 Mar 2025 11:04
Date: Mon, 10 Mar 2025 11:04
99 lines
3935 bytes
3935 bytes
On 2025-03-10 at 10:25 Konto58 wrote:
>> […] w przypadku chrony można synchronizację wymusić poleceniem
>> 'chronyc makestep' bez restartowania serwisu.
>
> chronyc makestep, powoduje u mnie wyłączenie synchronizacji
> System clock synchronized: no
timedatectl kłamie ;-)
# systemctl stop chronyd
# chronyc
tracking
506 Cannot talk to daemon
# timedatectl
Local time: Mon 2025-03-10 11:50:43 CET
Universal time: Mon 2025-03-10 10:50:43 UTC
RTC time: Mon 2025-03-10 10:50:43
Time zone: Europe/Warsaw (CET, +0100)
System clock synchronized: yes
NTP service: inactive
RTC in local TZ: no
#
NTP wyłączony, a on mówi, że czas zsynchronizowany?
Niczego nie wyłącza, trzeba po prostu chwilę zaczekać, chrony musi
sobie „pogadać” z serwerem NTP, co zwykle trwa kilkanaście, może
kilkadziesiąt sekund.
> więc trzeba ponownie włączyć
> timedatectl set-ntp yes
Nie, nie trzeba:
# chronyc tracking
Reference ID : C292FB65 (tempus2.gum.gov.pl)
Stratum : 2
Ref time (UTC) : Mon Mar 10 10:54:21 2025
System time : 0.000139052 seconds fast of NTP time
Last offset : +0.000480410 seconds
RMS offset : 0.001001170 seconds
Frequency : 3.860 ppm fast
Residual freq : +0.055 ppm
Skew : 9.495 ppm
Root delay : 0.015424609 seconds
Root dispersion : 0.002404715 seconds
Update interval : 65.3 seconds
Leap status : Normal
# chronyc makestep
200 OK
# chronyc tracking
Reference ID : C292FB65 (tempus2.gum.gov.pl)
Stratum : 2
Ref time (UTC) : Mon Mar 10 10:54:21 2025
System time : 0.000000000 seconds fast of NTP time <<<<<<<<<<<
Last offset : +0.000480410 seconds
RMS offset : 0.001001170 seconds
Frequency : 3.860 ppm fast
Residual freq : +0.055 ppm
Skew : 9.495 ppm
Root delay : 0.015424609 seconds
Root dispersion : 0.002472336 seconds
Update interval : 65.3 seconds
Leap status : Normal
# ############ I po minucie: ###########
# chronyc tracking ###### I po minucie:
Reference ID : C292FB65 (tempus2.gum.gov.pl)
Stratum : 2
Ref time (UTC) : Mon Mar 10 10:55:26 2025
System time : 0.000209958 seconds fast of NTP time
Last offset : +0.000217637 seconds
RMS offset : 0.000952284 seconds
Frequency : 4.393 ppm fast
Residual freq : +0.106 ppm
Skew : 7.932 ppm
Root delay : 0.015424609 seconds
Root dispersion : 0.003129392 seconds
Update interval : 64.2 seconds
Leap status : Normal
Technical Details
Message-ID:
<vqmgvh$19uu3$1@dont-email.me>Path:
mbox-mo1.pugleaf.net!news-archive.icm.edu.pl!news.icm.edu.pl!newsfeed.pionier.net.pl!2.eu.feeder.erje.net!feeder.erje.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mailReferences:
<vqgt6k$1mu3$1@dont-email.me> <87y0xf21fk.fsf@alfa.kjonca> <vqi2cj$75qh$2@dont-email.me> <87ldtf1hp4.fsf@alfa.kjonca> <vqi4lt$75qh$3@dont-email.me> <vql3tn$sje1$1@dont-email.me> <20250310102505.354829a9@lapek>Show Full Headers
Complete Article Headers
Path: mbox-mo1.pugleaf.net!news-archive.icm.edu.pl!news.icm.edu.pl!newsfeed.pionier.net.pl!2.eu.feeder.erje.net!feeder.erje.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail From: marrgol <marrgol@address.invalid> Newsgroups: pl.comp.os.linux Subject: Re: Synchronizacja czasu Date: Mon, 10 Mar 2025 12:04:17 +0100 Organization: A noiseless patient Spider Lines: 101 Message-ID: <vqmgvh$19uu3$1@dont-email.me> References: <vqgt6k$1mu3$1@dont-email.me> <87y0xf21fk.fsf@alfa.kjonca> <vqi2cj$75qh$2@dont-email.me> <87ldtf1hp4.fsf@alfa.kjonca> <vqi4lt$75qh$3@dont-email.me> <vql3tn$sje1$1@dont-email.me> <20250310102505.354829a9@lapek> MIME-Version: 1.0 Injection-Date: Mon, 10 Mar 2025 12:04:18 +0100 (CET) Injection-Info: dont-email.me; posting-host="a3750ba851c1ee5b91b6ddee82f17966"; logging-data="1375171"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19Cmc9pIDgZoborFaPQ4UJ3" User-Agent: Mozilla/5.0 (rv:102.0) Gecko/20100101, Betterbird/102 Cancel-Lock: sha1:kklv73UHO089RcmZ5q4LL25KT38= In-Reply-To: <20250310102505.354829a9@lapek> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit