[Bug 3277] [Feature req] "I couldn't do something you asked" warning

[bugzilla-daemon at dp3.samba.org]

https://bugzilla.samba.org/show_bug.cgi?id=3277


foner-rsync-bugzilla at media.mit.edu changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |foner-rsync-
                   |                            |bugzilla at media.mit.edu




------- Comment #2 from foner-rsync-bugzilla at media.mit.edu  2005-12-08 16:16 MST -------
I think what I'd like to see is a single option called --strict or something
(surely there's a better name) which I can either set all the time (e.g., by
calling rsync via an alias that sets it), or a corresponding environment
variable I can set in my init.  (And, of course, either/both would have to take
--nostrict so I can turn it off on a case-by-case basis if necessary.)  If I
have to remember to set a separate option, I'll probably forget, and that's
exactly what I'm trying to avoid---I typically wind up typing (or scripting,
even worse) some rsync command and then realizing days or weeks later that I
-meant- to get owners/groups set but didn't happen to run the command as root,
by which point it's way too late. And this seems conceptually simpler to me
than the peculiar other ways of specifying owner/group you mention below--and
extensible to other cases where the user may want to know that rsync wasn't
quite able to fulfill the request (e.g., ACL's or timestamps maybe).

I'm not sure whether it should complain on every file or just issue a warning
at the end, though.  The former might produce a lot of output, but OTOH, it'd
sure be hard to miss, and you'd only get it if you said --strict in the first
place...


-- 
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.