| Re: [chrony-users] Chrony and systemd-timesyncd |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: "chrony-users@xxxxxxxxxxxxxxxxxxxx" <chrony-users@xxxxxxxxxxxxxxxxxxxx>
- Subject: Re: [chrony-users] Chrony and systemd-timesyncd
- From: Jan Claußen <jan.claussen10@xxxxxx>
- Date: Fri, 12 Jul 2024 14:34:42 +0200
- Cc: "chrony-users@xxxxxxxxxxxxxxxxxxxx" <chrony-users@xxxxxxxxxxxxxxxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=web.de; s=s29768273; t=1720787556; x=1721392356; i=jan.claussen10@xxxxxx; bh=GZEqhPo13J5mf2g084CKbWFt9HVNxNFwPtZleZWGsRs=; h=X-UI-Sender-Class:Date:From:To:Cc:Message-ID:In-Reply-To: References:Subject:MIME-Version:Content-Type:cc: content-transfer-encoding:content-type:date:from:message-id: mime-version:reply-to:subject:to; b=jM2LjpKhifqPD8sEwp3fY5dlP6d16+96BCB+2wjEDDDanxPCZFLiaD3kwQP76fUX fFspvDpoKJIenX5uDf4u+PxexKxHxlYlES4q680hvEi0kOmsEwWaIiZ5JRC0bbV2d E+m9eVQ+Eyt1MCPjTPYV7kenlJdqf7zSafvIscA1A0un4+cgddTJGCoeqYztaZ6kO iq5ziPYy0YXdvOIw2jCa3GO3S3VwssW+kNJPIuNCcNlEY9Vq31odVyJYJz0E4M01F v9k5vfUrcM4GrXme0lL6YtICAEEhxQtxsX+AXZ+RP0h/dVRKFwhoWlhbUEqxhjQJM kYk9qM/W162X+1MidA==
- Ui-outboundreport: notjunk:1;M01:P0:DKE5FbvKAL4=;/iYNS7HfHn4XiOVX/T18vECEtju vc4OKUcIW+UXJIz4m5HLHhyNlwIusl5nYwuTLJoXibYMvlh9tGEV2kc0g0qSVqf5ZSHq7srKK 41WeaaAG0jUoCjyEvX8Y+fvnbDV+XJ5eFOFsQ+gW9VAQ9WtSLj2DNazlj19fSVjXAbkQ9YQER LPKu7iMpjxwySijGq7DDQM3sO+HqALqoC3obuDivWo9oXyhW5uxk/MsPYbmbbToEPSK93+Oov KcmKWySCOhkM7mENzuF+KnMedDAXuEEoRyM09ZgzVcUm3W3DBIZOgkE29SIiPNc+4yf8Pr8aQ NklKtn+3pwGaFrM/aW7oD4zCuhlJp4bs+Rtnrx03/RxPbHg/Qr2fEFmcQ7tLkh8U+fsJRA2Di lDrPpfXD9JMtiRXuYUoqrZmiuNSmCmJfCG2w7tLG+oL94YTN4eKpy+r66AgLqsrqv+jlcH3nb E2Ir3nkHUCFzbw25NlZOFm5nrOhuszB7xCFFNEjd8fkG0qeenAyhgMpyeJnA7SN1b8pbORjH9 OuwKingTxbkh6jC7KmLGcv8hizydrDpUorT0T6O98QjLR80CZyZxX4V+edYsEKhdb4MwIx0LS 2d9vUpq+RF9TKW2aOBqUc8m4TfwW1ZE21ztzdJGWnLSywdr44HSK5DlLaJ0m+lvx2idGJHSRM 4oY7AQJS2jUUgUJhB5R+gRi+YewQ5spMBSXXWtvFD5EzcpUROcE5Ut9QWuBJVchCt2U8uCeYw fZjgVpKbBCOnjaFAS4+hwY3UHycC2LKNiS5etBp5H7jB4N7KihXzGZq5yysqYrG0znK7Dt+gG pA4IQJLSzbWEJ2IU71gQO2lw==
Why do application require a specific time synchronisation tool?!
It is not obvious to me either. Neither systemd nor ntpd are listed as dependencies. One of the packages failing to build is net-snmp. Might be related to system time somehow. systemd is deeply interwoven with the system. The timedatectl timesync-status command will start timesyncd which conflicts with chrony. It is just hard to get rid of it, although probably not impossible.
Well, if you cannot change them, maybe you can configure timesyncd to synchronise to localhost?
What do you mean by synchronize to localhost? Unfortunately you can't configure timesyncd as thoroughly as chrony.. Have not found an option to have it not set the RTC or whatever. It is pretty much automated.
On Juli 12 2024, at 2:23 pm, Jan Claußen <jan.claussen10@xxxxxx> wrote:
systemd-timesyncd implements SNTP, it periodically updates system
time. chronyd will perceive it as erratic time jumps which will
probably result in rather bad quality for external clients.
What do you mean by bad quality? I know chrony is supposed to be more correct, but I think the SNTP quality would be enough for my needs. As long as there are no major issues, this would be fine for me.
I am not sure what you call a "hardware clock" here. For me RTC *is*
hardware clock.
From my understanding the hardware clock is the RTC as opposed to the system clock which is manged by the kernel in software.
My understanding is that chronyd will simply get whatever system time there is.
This is why I am asking whether it is the hardware clock or system clock. Would be nice if this could be specified the config. It is probably possible
On Juli 12 2024, at 2:06 pm, MUZZULINI Frank <Frank.MUZZULINI@xxxxxxxxxxxxxx> wrote:
![Sent from Mailspring]()