RussellMc wrote:

>>> AIUI, rsync is "semi-automatic": you need to give it a sync
>>> direction, or otherwise manually resolve whether a file missing in
>>> one location is copied to the location where it is missing or
>>> deleted at the location where it exists.
>=20
> That's a veryimportant consideration.
> In this context of 'follow me and do what I do" at BOTH ends, what you
> are trying to synchronise is NOT folder contents but actions.
>=20
> If you have two folders with contents
>=20
>             A B C       &    A B C D
>=20
> should yiu copy D to th elft hand folder or delete D from the right hand =
folder.
> Without extremely subtle or full time history logging you need
> something which tracks intention at each end.
>=20
> One possible way is to delete to a discard folder and synchronise what
> happens with that at the other end before hard deleting.

The other is, as I wrote, using a "master" repo where you don't work
directly, and make sure that the synchronization runs often enough so
that it is reasonably certain that a sync has been run before you get to
another machine.

Another is to use a program that hooks into the file system and records
actions. It doesn't know about intent, but it knows about what happened.
TechSoft's MirrorFolder is such a program, that may be of help setting
something up that works.

> My solution is, to the maximum point possible, never delete anything.

Deletion is not the only problem. Renaming is just as problematic, as is
editing on two systems before sync of the first edit did happen (the
latter in a different way, but still).

One relatively safe way is to use a version control system on the
server, and use locking checkouts. Has its own set of problems, though
:)

Gerhard
--=20
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.