RE: Improvement request: network status should not affect chronyc

> Have you tried 'chronyc -n sources', to avoid the reverse-DNS lookups?

No, I did not. Thanks for the hint. I was not aware of that. It solves my problem.

Thanks

Franz Hollerer

-----Original Message-----
From: Kevin P. Fleming <lists.chrony-users-OTXIk8dSW/[email protected]> 
Sent: Dienstag, 12. Dezember 2023 13:10
To: [email protected]
Subject: Re: [chrony-users] Improvement request: network status should not affect chronyc

On Tue, Dec 12, 2023, at 07:07, Hollerer Franz, Schrack Seconet AG, Entwicklung wrote:
> I have an improvement request for chronyc, more precisely its sources 
> command. I call "chronyc sources" via popen() from a C program to 
> determine if the system time can be considered synchronized or not.
>
> Unfortunately, if the network cable is disconnected, it takes about ~
> 15 seconds for "chronyc sources" to complete. The initial connection 
> to chronyd takes place immediately, also the header of the commands'
> output is print immediately. But then there is a very long delay till 
> the line with the NTP server status is printed.

Have you tried 'chronyc -n sources', to avoid the reverse-DNS lookups?

--
To unsubscribe email chrony-users-request-kWFZVVI9zxvPqho9SqqRMmD2FQJk+8+b@public.gmane.org
with "unsubscribe" in the subject.
For help email chrony-users-request-kWFZVVI9zxvPqho9SqqRMmD2FQJk+8+b@public.gmane.org
with "help" in the subject.
Trouble?  Email [email protected]


-- 
To unsubscribe email chrony-users-request-kWFZVVI9zxvPqho9SqqRMmD2FQJk+8+b@public.gmane.org 
with "unsubscribe" in the subject.
For help email chrony-users-request-kWFZVVI9zxvPqho9SqqRMmD2FQJk+8+b@public.gmane.org 
with "help" in the subject.
Trouble?  Email [email protected]