| Re: [chrony-users] Possible bug in PPS support |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] Possible bug in PPS support
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Wed, 25 Oct 2017 08:29:41 +0200
- Authentication-results: ext-mx08.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
- Authentication-results: ext-mx08.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=mlichvar@xxxxxxxxxx
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 9E1C3C05972E
On Tue, Oct 24, 2017 at 11:14:21PM +0200, Rob Janssen wrote:
> I am now monitoring the Root dispersion and this appears to work OK, after some tweaking
> of the threshold value. The reference time unfortunately is in a format that is not easy to
> check for "being recent" in a simple script, it would be nice if there was a "seconds since epoch"
> field as well (as there is in ntpd/ntpq).
With the -c option, which is available in newer chrony versions, the
reference timestamp is printed in "seconds since epoch".
$ chronyc -c tracking | awk -F , '{ print $4 }'
1508912704.491908798
--
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.