Hi,
I've had some issues with rsync over ssh with version 2.4.4 which an update
to 2.4.6 fixed. The problem I have now is that machines which do not have a
valid reverse dns entry for their IP addresses get empty directory listings
from the server, even though they can get the module list and
Welcome to the rsync list, Phil. Martin and David provided excellent
responses, but there's one more small point I want to make:
On Wed, Dec 12, 2001 at 03:42:59PM -0800, [EMAIL PROTECTED] wrote:
...
The main drawback I can see to exchanging hashes by
default is the extra receiver CPU time
This really is a minor point because as Martin pointed out, the fact that
rsync's pipelining would be defeated means that the idea would have a
drastic effect on throughput.
Okay, everyone has convinced me that my problem (excessive traffic in
the reverse direction) is best solved by simply
On Wed, Dec 12, 2001 at 08:26:31PM -0500, Ron Kelley wrote:
Does rsync support a user-defined compression level option (similar to
gzip)? I have read through the mailing list archive and could not find any
specific thread which addresses this question.
I would like to specify a medium
On Thu, Dec 13, 2001 at 01:52:35PM +0100, Matthias Saou wrote:
Hi,
I've had some issues with rsync over ssh with version 2.4.4 which an update
to 2.4.6 fixed. The problem I have now is that machines which do not have a
valid reverse dns entry for their IP addresses get empty directory
