Please disregard this message. I was copying older data.
Satadru
On Oct 27, 2004, at 9:35 PM, satadru pramanik wrote:
I'm doing a recurring copy from one server to another from the crontab
in this fashion:
rsync -av -e ssh --delete 10.0.1.18:/dir1/ /dir1 --progress &>
/var/log/rsync_backup.log
I'm doing a recurring copy from one server to another from the crontab
in this fashion:
rsync -av -e ssh --delete 10.0.1.18:/dir1/ /dir1 --progress &>
/var/log/rsync_backup.log
However, rsync is creating the dir /dir1/dir1 on the machine running
this job instead of updating the /dir1 folder.
On Tue, Sep 28, 2004 at 08:55:33AM -0700, Wayne Davison wrote:
> On Tue, Sep 21, 2004 at 12:37:55PM +0500, Sergey Golovin wrote:
> > I'm unable to write with remote rsync in daemon mode.
>
> The strace you included shows that it is the fork() call that is
> returning -1 (EAGAIN). So, you need to
Are there any characters that can occur in filenames that will choke
rsync?
We're transferring lots of data, and some of our users' filenames appear
to have their high bit set.
I don't expect it to cope with filenames having a \0 or / in them
(sometimes created over appletalk shares - strange bu
