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
Scott Russell <[EMAIL PROTECTED]> writes:
> [root@linux ftp-mirror]# ls -al
> total 8
> drwxr-xr-x 2 root root 4096 Feb 16 13:35 .
> drwxr-xr-x 29 root root 4096 Feb 16 13:16 ..
> lrwxrwxrwx 1 root root 57 Feb 16 13:35 RedHat ->
>../../home/ftp/pub/distr
[EMAIL PROTECTED] writes:
> Trying to run rsync as a daemon and use crontab to transfer files
> intermittently.
> Running rsync 2.4.6 and have OPENSSH 2.3.0
>
> get the following error when I do command
>
> SERVER1# rsync /home/testpage SERVER2:/home/testpage
> SERVER2: Connection refused
> u
