|AW: AW: [chrony-users] chronyd: Can' Synchronize WHY ?|
[ Thread Index |
| More chrony.tuxfamily.org/chrony-users Archives
- To: <chrony-users@xxxxxxxxxxxxxxxxxxxx>
- Subject: AW: AW: [chrony-users] chronyd: Can' Synchronize WHY ?
- From: <thomas.schmid@xxxxxxxxx>
- Date: Mon, 12 Sep 2011 19:21:32 +0000
- Accept-language: de-CH, en-US
- Thread-index: Acxt0eoyEKrFlFghQqmmfEP3FHpkcv//9VIA//++9cCAAJExAP/+ddwQgAODtID//9bGoAAH0pYAAAywRCsAAc4LAAAV/NKkABCsd4AAVZ2sAAAUTSuG
- Thread-topic: AW: [chrony-users] chronyd: Can' Synchronize WHY ?
>From the older measurements log it seems that peer delay is stable at ms
>level. If the problem was that chrony is often preempted, I'd expect
>the peer delay to be much worse.
>Maybe this would show that it's not the case:
>$ grep ctxt /proc/`pidof chronyd`/status
Hm, I don't know what "good" or "bad" values are, but here you are:
PC9: still switching (without the application running !):
PC6: no longer switching, as all server are on "noselect":
PC3: never switching, as only 1 source is configured:
PC4: still switching, despite "reselectdist 5" in its config:
PC18: still switching, despite "minstratum 2" on 2nd reference
PC19: no switching
So the number of non-voluntary context switches of PC9 seem very
high, but just on this PC the application is no longer running.
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.