https://bugzilla.samba.org/show_bug.cgi?id=3653
j...@jwz.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |j...@jwz.org
------- Comment #17 from j...@jwz.org 2010-10-01 11:27 CST -------
"Me too."
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?
Option A is bad because everyone gets to introduce differently-subtle bugs in
their script (wrong error code? accidentally ignoring too many error messages?
who knows. It's fragile.)
Option B is bad because I don't *want* to have a bunch of --exclude options for
my backup: disk and bandwidth are cheap, so I want my backup disk to be an
exact mirror. That way, when the disk holding / dies, I can just drop the
backup in and boot it, being confident that everything is exactly the same.
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
--
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
