Hi,
Thanks very much for the new info! It seems that you were right on the money
with what I had been trying to do and also, your suggestion of using
--relative switch can become useful, and I will implement it in my rsync
code.
I'll update you on this issue later on.
Shai
On 2/4/07, Matt McCu
On Sun, Feb 04, 2007 at 10:45:28AM -0500, Timothy J. Massey wrote:
> Why is the rsync client's connection all of a sudden not being
> recognized? Is the client sending the packets differently, or is
> iptables recognizing them differently?
Rsync just opens a socket and writes data to it (as wel
On Sat, Feb 03, 2007 at 04:22:01PM -0500, Matt McCutchen wrote:
> I think it would be helpful for the options in the man page to be
> divided into sections based on which aspect of rsync's behavior they
> affect.
That's seems like a good way to improve things. I have been grouping
options in the
On Sun, Feb 04, 2007 at 06:47:57PM +0200, catam wrote:
> shouldnt dir a came before a-c ?
Directories have an assumed trailing slash on the end of their name for
the purposes of sorting, which is why a-c/ comes before a/. The reason
for this is that older versions of rsync used to sort files from
On 2/2/07, Shai <[EMAIL PROTECTED]> wrote:
The new Debian Sarge server I built is using 2.6.9 version of rsync which
before, was not that new. It used to work fine (as far as I can tell you)
that sending a single file, would also create the directory if it did not
exist. Am I wrong to say this? E
Hi
While I was working on a script that uses rsync file list found this:
(which I guess is due adding / for dirs in f_name_cmp)
==2 dirs:
# mkdir a a-c
# rsync -a .
drwxr-xr-x 96 2007/02/04 18:20:35 .
drwxr-xr-x 48 2007/02/04 18:20:35 a-c
drwxr-xr-x 48 2007/02/04 18:20
Hello!
I have a consistent, reproducable failure performing an rsync of an
RHEL4 system running rsync in daemon mode with iptables enabled. With
iptables disabled, or with a rule that explicitly allows all traffic,
the rsync completes. However, with iptalbes enabled, the rsync starts,
but w
