On Thu, Jan 27, 2011 at 11:17 AM, Ron Aaron <r...@ronware.org> wrote:
> > I'm just doing an update, and get: > > Autosync: http://r...@dev.ronware.org/p/reva > Bytes Cards Artifacts Deltas > Sent: 130 1 0 0 > fossil: *** time skew *** server time differs by 67.1 seconds > Received: 2838 61 0 0 > Total network traffic: 351 bytes sent, 758 bytes received > > > My server and the client machine are within one second of each other, and > the > ping distance between them is under 1.2ms (avg). And I have the very > latest > fossil, 8854d6b6 > 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. Note that it is only a warning. You can ignore it if you like. -- D. Richard Hipp d...@sqlite.org
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
