On Fri, Jun 13, 2014 at 4:47 PM, Rick Thomas <rbtho...@pobox.com> wrote: > If you want to compare the local clock with a remote system's clock (often > called "skew"), the best way I know is with "ntpdate -qu". The "offset" it > mentions is the difference between your clock and the remote clock. Sadly, > "rdate -npv" doesn't give that information. >
Are you sure it doesn't? I'm seeing a very similar-looking number here: rosuav@sikorsky:~$ rdate -npv gideon Fri Jun 13 17:12:35 EST 2014 rdate: adjust local clock by 0.002302 seconds rosuav@sikorsky:~$ ntpdate -qu gideon server 192.168.0.13, stratum 3, offset 0.002310, delay 0.02589 13 Jun 17:12:42 ntpdate[32551]: adjust time server 192.168.0.13 offset 0.002310 sec The "adjust local clock by" line is provided by -v, although it doesn't show the delay (which, btw, seems rather high; gideon and sikorsky share a LAN, so I would expect a lot less than 25ms to get a response). ChrisA -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/captjjmpannoqtjcvn5mnoostn4p6dkxv-__srfdu1y+q4rv...@mail.gmail.com
