(Illustration by Gaich Muramatsu)
Hi, I have my home directory mounted on a coda volume and often get conflicts for no obvious reason. It usually turns out that one of the programs I was running created/updated a lock or temporary file. As these files are in various places all over my home directory, it is rather difficult to find them. Looking at the checkpointed CML sometimes gives a clue about which file to look at, 'find -lname "@*"' sometimes helps (usually times out on my machine, apparently my server responds too slowly to a big find). I'm quite sure venus knows which files are in conflict. Would it be possible to add a 'listconflicts' command to cfs that shows the locations of the conflicting files? At least for me it would save a lot of time. Another idea: currently, as soon as a volume gets write-disconnected because of a pending conflict, no updates on this volume at all are sent to the server, even those in non-conflicting files. Would it be possible to create a partial-disconnection mode where coda keeps sending updates of non-conflicting files to the server? Or maybe another cfs command that forces an update of non-conflicting files once. Next suggestion: I sometimes end up in disconnected operation because my token expired. cfs listvol just shows me that I'm disconnected but not why. By now I know that it's usually because of a missing token, but sometimes it takes a while to remember... Would be nice if cfs listvol reported a cause for disconnection (i.e. no valid token, no connection to server). Last but not least: repair always tells me coda_pioctl: Venus returns: -107 for (5cb1ff88.ff000001.00000001.00000001) WARNING: YOU DON'T HAVE TOKENS. YOU MIGHT WANT TO AUTHENTICATE FIRST even when I do have tokens (and repairing works). What am I doing wrong here? Thanks for the help JohannesReceived on 2004-05-28 00:43:28