sk you to look at the fchmod patch I also posted?
/assar
--
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
I posted a patch a few days ago that adds copying of atime. At that
time, it was just enabled with -t/--times. After some time, we have
figured out that that choice might not have been the best. Here's a
new version of the patch (relative to CVS) that adds -A/--copy-atime
instead. It also inclu
eful.
So, can anyone tell me any reasons for having the fchmod there? And
if there are none, would anyone object to removing it? A simple patch
for that is appended. Thanks.
/assar
Index: proto.h
===
RCS file: /cvsroot/rsync/proto.
st) for me on a:
Linux Debian/3.0 gcc 2.95.4 (debian), glibc 2.2.5 system.
Any questions/feedback? I certainly think that this functionality
would be useful for others. Note that this is orthogonal to updating
(or not) the atimes on the source tree.
/assar
Index
Elijah P Newren <[EMAIL PROTECTED]> writes:
> Yes, I understand that. But why can't rsync go back and set the
> modification time (and anything else that might be necessary)
> appropriately so that an exact mirror is created instead of an
> approximate one?
That's what it does. What makes you th
Elijah P Newren <[EMAIL PROTECTED]> writes:
> P.S. If it isn't a bug, could someone describe to me why this is
> expected behavior? I asked the sysadmin about it and he says it looks
> like a bug to him.
Well, there is a reason for this behaviour. Rsync has to create the
destination directories
Scott Sipe <[EMAIL PROTECTED]> writes:
> May 31 19:30:49 boud rsyncd[81707]: /etc/pwd.db: No such file or directory
>
> The file is definitely there, and readable.
The server is looking for a /etc/pwd.db in the chroot tree.
> boud# ls -l /etc/pwd.db
> -rw-r--r-- 1 root wheel 40960 May 22 08:0
e caused by the rsync server making a chroot() to
/var/ftp-mirror, thus failing to follow the symbolic links into
home/ftp. No chroot occurs when using ssh a transport. So you can
try adding 'use chroot = no' or re-organizing your tree.
/assar
an do a trivial command, such as
`rsh server2 hostname' first.
/assar
