Re: [coldsync-hackers] Hotsync proxy to coldsync ...

[JD Smith <jdsmith@astro.cornell.edu>]

Andrew Arensburger wrote:
> 
> On Mon, Nov 05, 2001 at 12:53:07PM -0500, JD Smith wrote:
> > I've always fancied (in ~/.palm/backup):
> > % rsync -e ssh --progress -Cuavz othermachine:.palm/backup/ .
> > % coldsync -F
> > % rsync -e ssh --progress -Cuavz . othermachine:.palm/backup/
> 
>         True, but rsync (or rdist, with which I'm more familiar)
> doesn't know anything about PDB records, does it? So it can't
> distinguish between a record added on host A, and the same record
> deleted on host B. Hence, you have to be careful to run rsync manually
> before syncing with the Palm.
>         All of this is fine if you remember to do it, but in an ideal
> world, I'd also like to have a more fire-and-forget method of syncing.

Hmm... yes. I have my Palm-sync command do a pre-pull and post-push sync
of the backup directory using rsync, so it's automated for me.  The
point is, Host B is made to be an exact replica of Host A before
syncing, and visa versa post-sync.  This works for me, because I'm using
Host B as merely a portal for syncing... i.e. it doesn't otherwise
modify its databases.  If it did (e.g. if I were using a calendar
program on Host B that modified Datebook.pdb), I have a different
situation, and need to make some assumptions to solve it (as coldsync
has done in the generic sync conduit)... keep both records, pick one,
etc.  

Even if you are modifying local records on both A & B, if you can avoid
simultaneous changes on both between syncs (e.g. if you work on Host A
at work and Host B at home), you can always get perfect syncing.  
That's not to say you'll actually remember...

JD
This message was sent through the coldsync-hackers mailing list.  To remove
yourself from this mailing list, send a message to majordomo@thedotin.net
with the words "unsubscribe coldsync-hackers" in the message body.  For more
information on Coldsync, send mail to coldsync-hackers-owner@thedotin.net.