We're trying to switch from ntp to chrony, so ntptime is still in use for the time being, thanks for your reply. -----邮件原件----- 发件人: Bill Unruh <[email protected]> 发送时间: 2024年1月3日 13:24 收件人: [email protected] 抄送: liaichun <[email protected]>; Yanan (Euler) <[email protected]> 主题: Re: [chrony-users] ntptime returned error 5
Why would you use ntptime with chrony? They are different processes, and there is no reason that chrony would impliment ntptime. ntptime is now about 40 years old. Why would you want to use it? William G. Unruh __| Canadian Institute for|____ Tel: +1(604)822-3273 Physics&Astronomy _|___ Advanced Research _|____ Fax: +1(604)822-5324 UBC, Vancouver,BC _|_ Program in Cosmology |____ [email protected] Canada V6T 1Z1 ____|____ and Gravity ______|_ theory.physics.ubc.ca/ On Wed, 3 Jan 2024, chengyechun wrote: > [CAUTION: Non-UBC Email] > > Hi all > > If chronyd is used as the local clock source, ntptime does not seem to > work properly, because of chrony's design or what configuration can control? > > The following is the local configuration. > > chronyd -p: > > > > driftfile /var/lib/chrony/drift > > makestep 1.0 3 > > rtcsync > > allow all > > local stratum 10 > > ntsdumpdir /var/lib/chrony > > logdir /var/log/chrony > > > > ntptime command output: > > ntp_gettime() returns code 5 (ERROR) > > time e93f3fcd.1f79d000 Wed, Jan 3 2024 10:07:09.122, (.122952), > > maximum error 16000000 us, estimated error 16000000 us, TAI offset 0 > > ntp_adjtime() returns code 5 (ERROR) > > modes 0x0 (), > > offset 0.000 us, frequency 0.000 ppm, interval 1 s, > > maximum error 16000000 us, estimated error 16000000 us, > > status 0x40 (UNSYNC), > > time constant 3, precision 1.000 us, tolerance 500 ppm, > > > N�����r��y隊W!���ǫ�����-r�+n��\�� "�����r��z)��.n7��Z+��izf���k�|�����z�\��'�۱}���*+�����)��.n7��:蹹^f��X��f���܆�'�۱}���*+
