On Thu, Nov 01, 2001 at 06:04:02PM +0800, Xuefeng wrote:
> Coda 5.3.13(what is ur version?). What I did was as follows: after
> reproducing the conflicts you have come across, I did not make use of the
> "repair" utility. I just re-initialize the venus on the machine having the
> conflict and Coda helps me to resolve the conflict automatically, if not

Ehh, in that case why don't you just use 'cfs purgeml' to discard any
of the logged operations. I hope you do realize that you are losing data
this way.

> magically. ;-) I believe Coda can resolve some conflicts by itself according
> to the time stamps of files and directories. It is prone to conflicts if the
> system time of machines running Coda are not synchronized.

Nahh, timestamps are no problem. The only wart in Coda that doesn't
really deal with unsynced clocks are the updateclnt/updatesrv daemons
that don't propagate the shared server databases correctly when the
server clocks are out of sync. Another clock problem is RVM, which
refuses to load whenever the system clock has jumped back.

Coda servers and Coda clients themselves have no problem with time
discrepancies. In fact, my laptop isn't really synced up with anything
and typically runs about 5-10 minutes 'off'. You might see problems
with userspace applications like make or biff that are trying to rely
on bad file modifications times that were written by an out of sync
client.

Jan