Yep, Unison is the way to go. I use it pretty heavily and love it. I
tend to use it interactively these days but there was a while when I had
a cron job with unison. *Most* of the time, there were no commits so no
issues... but since I had cron email me the output every day, I could
see the problems. Had I cared more, I could have written a procmail
rule to parse through the status emails looking for the conflicts.
Shawn Badger wrote:
> That is more like what I want. The only problem I see with it is the
> conflict resolution. I need it run in a cronjob non-interactively. I may
> be able to have it send me an e-mail when it has a conflict though and I
> go in and manually resolve it.
>
> On 11/6/07, *Dan Lund* <situationalawareness@gmail.com
> <mailto:situationalawareness@gmail.com>> wrote:
>
> There's an application called unison that'll take care of
> bidirectional synchronizations pretty easily.
> http://www.cis.upenn.edu/~bcpierce/unison/
---------------------------------------------------
PLUG-discuss mailing list -
PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
(text/plain)
