Re: Treat files that were modified locally and remote
On Sat, Feb 28, 2009 at 01:31:32PM +0100, Kurt wrote: One way to identify such files would be to do a dry-run upsync, then a dry-run downsync, find files that would have been sync'ed in both dry-runs, and then prompt the user for some action. Assuming that you mean to use the -u option, that still wouldn't work very well because you don't know if the updated file is newer than the original file, or a newer change than the also-changed file on the other side. You need something with a DB, such as unison, or (perhaps) the drsync perl wrapper script. ..wayne.. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Treat files that were modified locally and remote
On Sat, 2009-02-28 at 13:31 +0100, Kurt wrote: Hi - is there a clever way to identify files that have been change on the local _and_ the remote location? Without such a check it may happen, that changes are lost without even noticing. One way to identify such files would be to do a dry-run upsync, then a dry-run downsync, find files that would have been sync'ed in both dry- runs, and then prompt the user for some action. Is anybody aware of a shell script doing this, or is there an other clever way to solve that issue? If conflicting modifications are a concern, you should probably be using a two-way synchronization tool such as Unison ( http://www.cis.upenn.edu/~bcpierce/unison/ ). -- Matt -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Treat files that were modified locally and remote
Hi - is there a clever way to identify files that have been change on the local _and_ the remote location? Without such a check it may happen, that changes are lost without even noticing. One way to identify such files would be to do a dry-run upsync, then a dry-run downsync, find files that would have been sync'ed in both dry- runs, and then prompt the user for some action. Is anybody aware of a shell script doing this, or is there an other clever way to solve that issue? Thanks, and best regards, Kurt -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
