| [chrony-users] Improvement request: network status should not affect chronyc |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: "chrony-users@xxxxxxxxxxxxxxxxxxxx" <chrony-users@xxxxxxxxxxxxxxxxxxxx>
- Subject: [chrony-users] Improvement request: network status should not affect chronyc
- From: "Hollerer Franz, Schrack Seconet AG, Entwicklung" <f.hollerer@xxxxxxxxxxxxxxxxxxx>
- Date: Tue, 12 Dec 2023 12:07:20 +0000
- Accept-language: de-AT, en-GB, en-US
- Dkim-signature: v=1; a=rsa-sha256; c=simple/simple; d=schrack-seconet.com; s=mail; t=1702382878; bh=6jkX4AzwfZx8/LxuqH04c3xMrNQ90RnaNarkfkTLjgI=; h=From:To:Subject:Date; b=uVwThJbidIcft/66UFRz0eJxosjwzVGZA7rlgsr7I7kEGBxw0/xTndghNLNJtYgiP P8DGorTZrzKU0xACYWtqK0FM5LqE3ZmHNLaSd/KuT1HuF+WHDiP5Fkx9PdssfDdwIJ 6XVQqz4XipimhrdKAuCaXu81uJuYn0DPvgkHcI40=
- Thread-index: Ados86WTMYkLPsAqTrK7R//o3UF0Vw==
- Thread-topic: Improvement request: network status should not affect chronyc
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.
This means that the disconnected network cable has a non-negligible negative effect on the command line interface (CLI), although chronyd and chronyc run on the same host.
It would be nice if the network status would not affect chronyc, i.e., chronyc completes promptly.
Thanks
Franz Hollerer
--
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.