Re-integrating After Disconnection

When you reconnect to the network after a disconnected session, Coda will automatically try to reintegrate your changes with the Coda servers. You must be authenticated before reintegration occurs. Watch the file /usr/coda/etc/console by running: tail -f /usr/coda/etc/console or look at more detailed progress using the codacon command. The reintegration status will be written to this file.

If the reintegration was successful, the log entries would look like:

Reintegrate u.raiff, (1, 244) ( 13:33:43 )
coda: Committing CML for u.raiff ( 13:33:43 )
coda: Reintegrate: u.raiff, result = SUCCESS, elapsed = 2640.0 (15.0, 2609.0, 
15.0) ( 13:33:43 )
coda:   delta_vm = 0, old stats = [0, 1, 0, 0, 0] ( 13:33:43 )
coda:   new stats = [   0,   0.0,     0.0,    1,   0.2], [   0,   0.0, 0.0,  0,   0.0] ( 13:33:43 )

The following example is from a failed reintegration on the volume u.raiff.

Reintegrate u.raiff, (1, 244) ( 13:27:10 )
coda: Checkpointing u.raiff ( 13:27:10 )coda: to /usr/coda/spool/2534/u.raiff@@%
coda%usr%raiff ( 13:27:10 )
coda: Aborting CML for u.raiff ( 13:27:10 )
coda: Reintegrate: u.raiff, result = 198, elapsed = 2437.0 (15.0, 2265.0, 531.0)  ( 13:27:10 )
coda:   delta_vm = 1000, old stats = [0, 0, 1, 0, 0] ( 13:27:10 )
coda:   new stats = [   0,   0.0,     0.0,    1,   0.2], [   0,   0.0, 0.0,   0,   0.0] ( 13:27:10 )

Notice that the change modify log (CML) was check-pointed to /usr/coda/spool/2534/u.raiff@@%coda%usr%raiff. This file is a tar file containing the changes that were made on during the disconnected session. The files in the tar file are relative to the root of u.raiff.

The file which failed to reintegrate will be in conflict and will need to be repaired with the repair tool as discussed in the section called Repairing an Inconsistent Directory.