>
> Can you reliably cause the problem to go away when you go back to 2.3.1 and
> re-appear when you go to 2.4.6?
>
No. Actually, when I backed out to 2.3.1 it didn't help. I went
forward again on both machines to 2.4.6, and although it takes ALOT LONGER to
run, it runs to completion.
I'm having problem on slackware,
rsyncd.conf file
uid = root
gid = root
pid file = /etc/rsync.pid
log file = /var/log/rsync
strict modes = false
[backups]
path = /backups/zeus/
comment = ZEUS BACKUPS
auth users = lucipher
secrets file = /etc/rsync.secrets
max connections = 30
use chro
i am running rsync from a shell script out of cron to transfer a module
between 2 solaris servers. I am getting the error "Argument too long". What
does that mean? I can run the rsync command without a problem from the
command line. Its only when the rsync command is started from inside the
shell
On Tue, Jun 05, 2001 at 09:25:12AM +0100, Gonçalo Gomes wrote:
> Dear rsync users,
> i'd like to ask some questions about rsync,
>
> 1) i'm going to use rsync to upload backups to "backup machine", that
> machine will hold only backups.
> - does it keeps the ownership of the files if the user
I've worked up a new --move-files option that doesn't delete the files
on the sending side until the receiver is known to have successfully
written the data. I didn't want to implement a delete-pass at the end
of the send since I wanted the files to get deleted as we go. However,
because of the
I think I've tracked down another hang in rsync 2.4.6. This one appears
to be caused by the sender process finishing up all its work and going
into a pid-reading loop before it finishes reading all the error stream
coming in from the generator process -- if this data is large enough,
the generato
Dear rsync users,
i'd like to ask some questions about rsync,
1) i'm going to use rsync to upload backups to "backup machine", that
machine will hold only backups.
- does it keeps the ownership of the files if the users/groups, they
don't exist in the remote machine (backup machines)
or i