Re: Question/comment about -n (dry run) flag of rsync
No problem On Tue, Mar 10, 2020, 18:05 raf via rsync wrote: > raf via rsync wrote: > > > T. Shandelman via rsync wrote: > > > > > Rsync is a remarkably handy tool that I use virtually every day. > > > > > > But there is one thing about rsync that drives me totally crazy. > > > > > > Under the -n (dry run) flag, rsync seems to produce exactly the same > output > > > as without that flag. > > > > > > I cannot tell you how many times I sit and scratch my head long and > > > hard,after I discover that my intended rsync operations did not > actually > > > happen. Until I finally remember that I ran rsync in dry-run mode. > That's > > > why! This is especially a problem for very long-running rsync jobs run > in > > > dry-run mode. > > > > > > It seems to me that when run in dry-run mode, rsync should display a > > > warning at the very, very end, something like: > > > > > > *WARNING: None of the above operations have been actually performed, * > > > *because you ran rsync in dry-run mode.* > > > > > > Or does rsync already have such a feature, and I am not aware of it? > > > > > > But if not, that is my vote for the next feature to be added. It > should be > > > a very, very easy fix. > > > > > > Todd S. > > > Austin, Texas, USA > > > > Bear in mind that it shouldn't happen by default as > > that could break scripts that parse rsync's output. You > > should need to request this behaviour in the config > > file somehow. > > Oops. Please ignore that. > > > -- > 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 > -- 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: Question/comment about -n (dry run) flag of rsync
raf via rsync wrote: > T. Shandelman via rsync wrote: > > > Rsync is a remarkably handy tool that I use virtually every day. > > > > But there is one thing about rsync that drives me totally crazy. > > > > Under the -n (dry run) flag, rsync seems to produce exactly the same output > > as without that flag. > > > > I cannot tell you how many times I sit and scratch my head long and > > hard,after I discover that my intended rsync operations did not actually > > happen. Until I finally remember that I ran rsync in dry-run mode. That's > > why! This is especially a problem for very long-running rsync jobs run in > > dry-run mode. > > > > It seems to me that when run in dry-run mode, rsync should display a > > warning at the very, very end, something like: > > > > *WARNING: None of the above operations have been actually performed, * > > *because you ran rsync in dry-run mode.* > > > > Or does rsync already have such a feature, and I am not aware of it? > > > > But if not, that is my vote for the next feature to be added. It should be > > a very, very easy fix. > > > > Todd S. > > Austin, Texas, USA > > Bear in mind that it shouldn't happen by default as > that could break scripts that parse rsync's output. You > should need to request this behaviour in the config > file somehow. Oops. Please ignore that. -- 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: Question/comment about -n (dry run) flag of rsync
T. Shandelman via rsync wrote: > Rsync is a remarkably handy tool that I use virtually every day. > > But there is one thing about rsync that drives me totally crazy. > > Under the -n (dry run) flag, rsync seems to produce exactly the same output > as without that flag. > > I cannot tell you how many times I sit and scratch my head long and > hard,after I discover that my intended rsync operations did not actually > happen. Until I finally remember that I ran rsync in dry-run mode. That's > why! This is especially a problem for very long-running rsync jobs run in > dry-run mode. > > It seems to me that when run in dry-run mode, rsync should display a > warning at the very, very end, something like: > > *WARNING: None of the above operations have been actually performed, * > *because you ran rsync in dry-run mode.* > > Or does rsync already have such a feature, and I am not aware of it? > > But if not, that is my vote for the next feature to be added. It should be > a very, very easy fix. > > Todd S. > Austin, Texas, USA Bear in mind that it shouldn't happen by default as that could break scripts that parse rsync's output. You should need to request this behaviour in the config file somehow. cheers, raf -- 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: Question/comment about -n (dry run) flag of rsync
If you used -v then the very last line rsync outputs is: total size is ### speedup is ### (DRY RUN) -- ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._., Kevin Korb Phone:(407) 252-6853 Systems Administrator Internet: FutureQuest, Inc. ke...@futurequest.net (work) Orlando, Floridak...@sanitarium.net (personal) Web page: https://sanitarium.net/ PGP public key available on web site. ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._., On Tue, 10 Mar 2020, T. Shandelman via rsync wrote: Date: Tue, 10 Mar 2020 17:26:41 -0500 From: T. Shandelman via rsync To: rsync@lists.samba.org Subject: Question/comment about -n (dry run) flag of rsync Rsync is a remarkably handy tool that I use virtually every day. But there is one thing about rsync that drives me totally crazy. Under the -n (dry run) flag, rsync seems to produce exactly the same output as without that flag. I cannot tell you how many times I sit and scratch my head long and hard,after I discover that my intended rsync operations did not actually happen. Until I finally remember that I ran rsync in dry-run mode. That's why! This is especially a problem for very long-running rsync jobs run in dry-run mode. It seems to me that when run in dry-run mode, rsync should display a warning at the very, very end, something like: *WARNING: None of the above operations have been actually performed, * *because you ran rsync in dry-run mode.* Or does rsync already have such a feature, and I am not aware of it? But if not, that is my vote for the next feature to be added. It should be a very, very easy fix. Todd S. Austin, Texas, USA -- 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
Question/comment about -n (dry run) flag of rsync
Rsync is a remarkably handy tool that I use virtually every day. But there is one thing about rsync that drives me totally crazy. Under the -n (dry run) flag, rsync seems to produce exactly the same output as without that flag. I cannot tell you how many times I sit and scratch my head long and hard,after I discover that my intended rsync operations did not actually happen. Until I finally remember that I ran rsync in dry-run mode. That's why! This is especially a problem for very long-running rsync jobs run in dry-run mode. It seems to me that when run in dry-run mode, rsync should display a warning at the very, very end, something like: *WARNING: None of the above operations have been actually performed, * *because you ran rsync in dry-run mode.* Or does rsync already have such a feature, and I am not aware of it? But if not, that is my vote for the next feature to be added. It should be a very, very easy fix. Todd S. Austin, Texas, USA -- 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: Encrypt destination file
Thank you so much. Regards, Dat Le From: Karl O. Pinc Sent: Sunday, March 8, 2020 5:33 PM To: Rainy Days via rsync Cc: Rainy Days Subject: Re: Encrypt destination file On Sun, 8 Mar 2020 15:49:43 + Rainy Days via rsync wrote: > My company have been using rsync to sync our file to a backup server > (running rsync daemon), and now we would like to store them > encrypted. I found some thread that discussed this issue but they are > pretty old (about 10 years ago). So I send this question again and > looking for any new approach. Is there any option or module for rsync > to encrypt file on the destination? Your easiest/best option is probably to encrypt the destination file system. "Best" is always relative. You have to look at your threat model. Regards, Karl Free Software: "You don't pay back, you pay forward." -- Robert A. Heinlein -- 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: Encrypt destination file
Thank you. I will investigate more about them. Regards, Dat Le From: rsync on behalf of rsync--- via rsync Sent: Tuesday, March 10, 2020 3:00 AM To: rsync@lists.samba.org Subject: Re: Encrypt destination file Rainy Days via rsync wrote: > Hi, > > My company have been using rsync to sync our file to a backup server (running > rsync daemon), and now we would like to store them encrypted. > I found some thread that discussed this issue but they are pretty old (about > 10 years ago). So I send this question again and looking for any new approach. > Is there any option or module for rsync to encrypt file on the destination? > > Thanks a lot, > Dat Le Hi, If the destination is Linux, you could maybe use ecryptfs to encrypt a section of the file system. Everything would still appear decrypted as long as the ecryptfs file system is mounted. But if you wanted it to look encrypted, then maybe you could mount it, rsync, then unmount it. Then it would at least appear encrypted most of the time (when rsync is not actively in use). But this sounds dumb. For rsync to do this automatically, it would need to be able to automatically decrypt files in memory at the destination in order to compare them to the source version which means having access to the decryption key at the destination. An option to run a process at the other end to filter each file for comparison would be needed. That would slow things down. Another option is to have full disk encryption at the destination. I know that this (and ecryptfs) still make unencrypted files accessible while the host is running, and so may not satisfy the needs of your threat model, but it does seem to satisfy the encryption-at-rest requirements of some governments for some purposes. Another approach (assuming Linux and ecryptfs), is to use ecryptfs at the source to store everything encrypted, use a mountpoint for the ecryptfs file system that isn't the same as the underlying directory so that the encrypted versions of the files are accessible (which they wouldn't be if the ecryptfs file system were mounted over the top of the underlying directory), and just rsync the underlying encrypted directory rather than the overlaid ecryptfs file system (where everything looks decrypted). This approach doesn't require any changes to rsync and it doesn't require the ability to decrypt the files on the destination host. But it does require Linux and ecryptfs at both the source and the destination. cheers, raf -- 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 -- 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
