What do you mean, altered? Do the destination files already exist?
It is supposed to preserve existing permissions on destination files
when you don't use -p.
- Dave
On Mon, Dec 30, 2002 at 06:44:24PM -0800, Ben wrote:
Hmmm... while that makes sense, that doesn't really help me in my
Then what would you expect it to do? I'm guessing your only problem is
that the chmod is failing, and you would rather have it create files with
the final permissions in the first place; is that it? I believe it is
done this way because of worries of potential security problems, where
temporary
Yeah, my problem is that the chmod fails, so then rsync complains not
everything worked as expected. Because I'm writing files to a network
mount with forced permissions, I would like a way for rsync to simply
create the file and never try to chmod what it creates. Normally that
would probably be
On Tue, Dec 31, 2002 at 08:06:52AM -0800, Ben wrote:
No, these are for new files. Existing files work perfectly, but, like
you said before, for new files rsync creates the file then attempts to
alter the permissions based on the origional permissions and umask.
On Mon, Dec 30, 2002 at
OK, now I understand. I have seen those errors also when writing onto a
PC filesystem mounted by Linux. Other programs like tar and cpio have
the same problem, so I've just ignored the messages. Maybe everybody
else does the same. Maybe a well thought out and documented patch for
a new flag
I'm relatively new to rsync, but it seems to me that if there's an
option to perserve permissions and you don't set it, then rsync
shouldn't do anything with permissions.
I think having chmod silently fail in the absence of -p works here as
well, but I may well not be thinking about all cases.
