On Thu, Mar 5, 2015 at 1:03 PM, Les Mikesell <lesmikesell at gmail.com> wrote:> On Thu, Mar 5, 2015 at 11:44 AM, Francis Gerund <ranrund at gmail.com> wrote: > > Hello. > > > > I think it is just too easy to make mistakes with rsync. And getting it > > "almost correct" can really get you hurt. > > What are you trying to do, and what kind of mistakes are you worried > about? The only things I find confusing are what the trailing / > means on a directory name and that -H isn't bundled with the other > options that -a includes that you normally want. You can avoid the > ambiguity of whether the top directory or just the contents will be > copied by cd'ing into the source directory and doing: > rsync -av . host:/path/to/dir. That is, by using '.' as the source > you can't mistakenly create another directory level on the target. > And you just have to remember that it will create the final directory > in the target path if it doesn't exist, but just the final one, not > the whole path. >The fact that you need a paragraph this long to describe how to avoid some of the confusion when using rsync pretty much speaks for itself. Rsync definitely has its own syntax and is much more sensitive than other unix tools, so it's not unwarranted that people might be confused. I don't know anyone who fully understands the include/exclude filters either, at least not without rereading the man page a few times.> And if you add -n or --dry-run to the options along with -v, it will > go through the motions and show you the files that would be > transferred without actually doing it. > > -- > Les Mikesell > lesmikesell at gmail.com >? Brian Mathis @orev
Thanks for the replies. 1) I always use the -n (--dry-run) option. Couldn't imaging not doing so! 2) I hate having to look up stuff like the trailing slashes each time. And trying to decide what to (--exclude), to -H or not to -H, etc. 3) I hate having to re-do #2 every time I want to do a small ad-hoc backup or synchronization, let alone a full filesystem backup. 4) I could do shut down, reboot, and run Grsync from a cd or USB stick. But what a hassle for minor, ad-hoc stuff. Should only have to do that for full backups. 5) If Grsync was in centos before, why was it removed? "Because it's not in RHEL." Okay, but why not? 6) While I do really appreciate CLI stuff, more and more I have come to appreciate GUI stuff. Someday, I think you too will understand. 7) Again, hasn't anyone installed Grsync in centos 7 from source? I hate to being the "lab rat".
On Thu, Mar 5, 2015 at 4:30 PM, Francis Gerund <ranrund at gmail.com> wrote:> > 3) I hate having to re-do #2 every time I want to do a small ad-hoc backup > or synchronization, let alone a full filesystem backup.If you are doing system backups regularly with manual command line runs, I'd recommend looking at backuppc (well I'd recommend it even more if you aren't doing regular backups...). But it works best with a 2nd system doing the work and might not be a replacement for rsync to a removable drive. -- Les Mikesell lesmikesell at gmail.com
On Thu, Mar 05, 2015 at 04:30:15PM -0600, Francis Gerund wrote:> 5) If Grsync was in centos before, why was it removed? "Because it's not > in RHEL." Okay, but why not?I can't find any evidence it was ever in RHEL or CentOS. It looks like it's in the Nux Desktop repo and the Repoforge repo for EL5 and 6 and Nux for EL7.> 6) While I do really appreciate CLI stuff, more and more I have come to > appreciate GUI stuff. Someday, I think you too will understand.I really doubt that. Someday, maybe, you'll understand why some people prefer the command line interface.> 7) Again, hasn't anyone installed Grsync in centos 7 from source? I hate > to being the "lab rat".The Fedora packages rebuild fine for epel7 (I just tested it), so I would assume that'd be the best place to start if you wanted to build your own packages. Or you could just use the Nux Desktop repo. See: http://wiki.centos.org/AdditionalResources/Repositories -- Jonathan Billings <billings at negate.org>