On Tue, Dec 01, 2009 at 10:42:52PM +0900, KOBAYASHI, Shinji wrote: > > > 0) Adjust all workstation using NTP server > > > > There seems to be no reason for this, if we don't have to keep our > > workstations in synch. > > > > > 1) Tim send me the file recorded 'event1', '2009-10-30T12:18:11BST' > > > 2) I received file and record it after change BST to UTC 'event1, > > > '2009-10-30T09:18Z' and record with timestamp. > > > 3) I send Tim with the file recorded 'event2', '2010-01-22T01:22:22JST' > > > > So you change the datetime on your workstation independently of the > > other workstations, right? > > I cannot understand what you meant in 'independently'. > For some authentication procedure, we need to sync date tome on our > workstation. So wee need 0).
Exactly. What was proposed was to not use an *official*, true-time, NTP time server but rather declare one local machine as *being* the *local* NTP time server for all other machines taking part in this connectathon. That way, time can be spun forward on just that one local time server and all other workstations can be expected to re-sync into the future via NTP within their re-sync timeout. Makes things a lot easier. > I think the time in record, when the event happened, does not depend on > the clock of the workstation. Sure, that's another approach. But using the local NTP approach one can *simulate* progress of real time, not just assume it. HTH, Karsten -- GPG key ID E4071346 @ wwwkeys.pgp.net E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
