> Doing nightly backups from cron is an *extremely* common use-case of rsync, > and > telling each and every user of rsync that they should either A) write their > own > shell script to filter and discard error messages, or B) play a constant game > of whack-a-mole chasing down new --exclude options to add, is just silly. It > pushes work downstream that could be done upstream much more efficiently. Why > make each user write the same code over and over when the developer could > write > it just once, and get it right?
You may want to take a look at LBackup : http://www.lbackup.org Just one rsync based backup possibility. Note : The current version 0.9.8r5-alpha3 of LBackup, requires a wrapper script to be put around rsync if you want to ignore the vanished files warning. : http://www.lbackup.org/developer/ignore_vanished_file_warnings Any assistance to improve rsync / LBackup is warmly welcomed. Perhaps one option is a new option to suppress this file vanished warning is a possibility? I would be interested to have other peoples take on such an approach. --------------------------------------------------------------------- This email is protected by LBackup, an open source backup solution. http://www.lbackup.org -- 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
