rdebath Posted May 1, 2013 Report Share Posted May 1, 2013 You think you might want to fix the date & time in the log file ... [20130401 20:58:58] Got id message from peer TestMachine (38D0F91A99C57D189416439CE377CCDCD92639D0) 1.0.125Notice it says the date is 20130401 not 20130501 for today.Milliseconds would be nice too. Quote Link to comment Share on other sites More sharing options...
Automatic Coding Posted May 1, 2013 Report Share Posted May 1, 2013 I would assume that the log is based on the local time of the computer that's logging, so, check that time? Quote Link to comment Share on other sites More sharing options...
rdebath Posted May 1, 2013 Author Report Share Posted May 1, 2013 The machine is running ntpd, so the time shouldn't be out by more than a few milliseconds. ...$ rdate -a -v -p -n ntp0.strath.ac.ukWed May 1 21:44:09 BST 2013rdate: adjust local clock by 0.020106 seconds$ ...Well, 20 milliseconds, is that close enough ? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.