> Fossil thinks that the timestamp on the message it received back from the > server is 67.1 seconds off from its own system clock. If your clocks are > synchronized, and the message is only taking a few milliseconds to travel > your network, then this should not be happening.
Very odd. I rebooted my client to no avail; but when I rebooted the server, the problem went away. That's a bit of a concern, since I can not think of any good explanation. Best regards, Ron _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
