Subject: RE: replicated DID error
From: Jonathan Newman (jnewman@mudpup.com)
Date: Tue Dec 19 2000 - 10:47:40 EST
> From: Mike Johnson
> Sent: Monday, December 18, 2000 11:48 PM
... snip ...
>
> Those two folders were called "viking" and "from_andrews_home". I renamed
> them to "viking2" and "from_andrews_home2". The copy kept moving,
> unfettered by this name change.
... snip ...
> Then, finally, a syslog entry:
>
> -------------------------
> Dec 18 15:16:00 challenger afpd[1765]: WARNING: DID conflict for 'pa' and
> 'pa2'. Are these the same file?
> Dec 18 15:16:00 challenger afpd[1765]: WARNING: DID conflict for
> 'from_andrews_home' and 'from_andrews_home2'. Are these the same file?
>
Interesting. This is one case I hadn't thought of. The DID database has
stale information in it. Sounds like we need to do an existence test of the
one found in the database on a DID conflict.
... snip ...
>
> I noticed that simply closing the windows yet still keeping the mac's
> challenger mount didn't refresh the windows. The only thing that
> successfully resolved the DID conflict was disconnecting from the server
> and connecting again.
This makes sense. The DID database is stored per client, and the only way
to "destroy" the database is kill the client (disconnect from the server).
Jon
This archive was generated by hypermail 2b28 : Wed Jan 17 2001 - 14:32:48 EST