A timewarp (clock skew) occurs when the discrepancy between the system clocks on a client machine and a server machine exceeds the allowable tolerance of 5 seconds. A timewarp can also occur in a replication environment, when the clocks on the master server and a replica server differ by more than 5 seconds. (See
Replication of the AccuRev Repository on page 45.)
Timewarp problems typically occur during initial system setup and during time zone adjustments. For example, the change from Eastern Standard Time to Eastern Daylight Time can cause a timewarp on a machine that is not configured correctly to handle the time zone adjustment.
For most AccuRev operations, a timewarp check is performed when the client contacts the server, or when a replica server forwards an AccuRev command to the master server.
Each time a client program contacts the server program — or a replica AccuRev Server contacts the master AccuRev Server — AccuRev compares the system clocks on the two machines. If the discrepancy is less than or equal to 5 seconds, AccuRev proceeds to execute the user’s command.
If there’s a timewarp exceeding 5 seconds between a client machine and a server machine and the user’s command specifies the
–t option with a time specification (not a transaction number), AccuRev uses the (case-insensitive) value of variable
AC_SYNC in the user’s environment to determine how to proceed:
client_time: 2008/07/14 10:54:54 Eastern Standard Time (1216047294)
server_time: 2008/07/14 10:49:56 EDT (1216046996)
timewarp: 298 seconds
The time on this machine is more than 5 seconds different than the
time on the server. Please fix this and try again.
You may have a problem with your system clock.
You can force the time on your system to match the server time
using the accurev synctime command.