| 答复: [chrony-users] Synchronous Version Switching |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
Thank you for your reply;
Is this a function later than chrony-4.0? Because I can still configure itself as the time source in chrony-3.5, and the same is true for NTP.
The scenario of synchronizing its own time is like an orphan network. You can use the driftfile configuration to meet the synchronization requirements of the client. Is that correct?
-----邮件原件-----
发件人: Miroslav Lichvar [mailto:mlichvar@xxxxxxxxxx]
发送时间: 2022年7月26日 18:46
收件人: chrony-users@xxxxxxxxxxxxxxxxxxxx
主题: Re: [chrony-users] Synchronous Version Switching
On Tue, Jul 26, 2022 at 09:40:41AM +0000, chengyechun wrote:
> Hello all:
> I'm using chrony version 4.1 on an embedded Linux system；127.0.0.1 cannot be synchronized in version 4.1, but it can be synchronized in version 3.5. Is this a difference? The following is my configuration file and the firewall is disabled.
> server 127.0.0.1 iburst minpoll 3 maxpoll 3
This is not a valid configuration. chronyd should never be synchronized to itself. The newer version can detect that and ignore the source.
You already have the local directive in the config. That is enough to provide time to clients when the server is not synchronized to anything.
--
Miroslav Lichvar
--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.