Hi, NB: I am only subscribed because the list doesn't allow non-subscribers to post by default. I find that a bit strange, especially for such a low volume list. Okay, I've thought about this for a while. Let's say you do an rsync as a dry run (deliberately), why not allow a state file to be saved (ala, like a cookie file which wget has as an option). Then if the dry run gives the right result, re-run it with the state file and ONLY effect the changes as they were presented by the prior dry run, perhaps abort if the changes would be different. The idea would be to do a dry run, make sure it looks good and /approve/ that resultant changes for a non dry run, rather than risk new differences creeping in since the original dry run. Kind Regards AndrewM
You can kind of do that with only-write-batch. Then replay the batch file. On April 1, 2018 16:02:14 Andrew McGlashan via rsync <rsync at lists.samba.org> wrote:> Hi, > > NB: I am only subscribed because the list doesn't allow non-subscribers > to post by default. I find that a bit strange, especially for such a > low volume list. > > Okay, I've thought about this for a while. > > Let's say you do an rsync as a dry run (deliberately), why not allow a > state file to be saved (ala, like a cookie file which wget has as an > option). Then if the dry run gives the right result, re-run it with the > state file and ONLY effect the changes as they were presented by the > prior dry run, perhaps abort if the changes would be different. > > The idea would be to do a dry run, make sure it looks good and /approve/ > that resultant changes for a non dry run, rather than risk new > differences creeping in since the original dry run. > > Kind Regards > AndrewM > > -- > Please use reply-all for most replies to avoid omitting the mailing list. > To unsubscribe or change options: > lists.samba.org/mailman/listinfo/rsync > Before posting, read: catb.org/~esr/faqs/smart-questions.html