On Fri, Oct 13, 2006 at 02:49:27PM +1300, Jason Haar wrote:
> However, how do you then do the same thing from the client end? I guess
> you can't? There's no "--dont-compress" option by the looks of it.
Correct, that's currently a limitation in rsync. It would make sense
to allow it, since the pr
Wayne Davison wrote:
> On Fri, Oct 13, 2006 at 01:08:54PM +1300, Jason Haar wrote:
>
>> Looks like rsync "decided" to compress data.gz even though
>> /etc/rsyncd.conf had "*.gz" in it's "dont compress" section...
>>
>
> That setting only affects files being pulled from an rsync daemon, not
On Fri, Oct 13, 2006 at 01:08:54PM +1300, Jason Haar wrote:
> Looks like rsync "decided" to compress data.gz even though
> /etc/rsyncd.conf had "*.gz" in it's "dont compress" section...
That setting only affects files being pulled from an rsync daemon, not
pushed to one. It seems that the manpage
I got curious as to how rsync operates, and got a few tests going under
ethereal. The results confused me more.
I created /tmp/test-out/ containing two different text files - one named
"file.txt" and the other "data.gz". ie. data.gz wasn't actually
compressed - it was actually text. I then created
