23, 2010 at 5:25 PM, Matt McCutchen wrote:
> On Tue, 2010-03-23 at 17:12 -0700, Bruce Korb wrote:
>> Fixing a spelling error for the log file name gets me the log text,
>> but not anything I understand:
>>
>> Unknown filter rule: `/gdoc/***'
>>
>> OK,
Fixing a spelling error for the log file name gets me the log text,
but not anything I understand:
Unknown filter rule: `/gdoc/***'
OK, I am trying to ensure that files pushed to the "doc" module all start
with the prefix "/gdoc/". My reading of the docs seems to say to me that
this is the way
Hi Matt,
On Tue, Mar 23, 2010 at 4:23 PM, Matt McCutchen wrote:
> "Yes" is the default, so you have to explicitly write "use chroot = no".
Done. No effect.
> --rsync-path='strace -f -o ~/rsync.strace rsync' to the client.
I now have an strace output file. It opens rsyncd.conf correctly
and r
does the "-e ssh" invocation of rsync actually load up rsyncd.conf ?
If not, that would explain why no logging. H. Maybe I need
to work out a daemon over ssh tunnel now?
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://li
Hi Matt,
Thank you again.
On Tue, Mar 23, 2010 at 3:57 PM, Matt McCutchen wrote:
>> its 873 port -- as long as it will use a secure encrypted tunnel.
>
> The rsync daemon protocol on port 873 does not support encryption or
> integrity protection, so an rsync daemon over ssh may actually be just
Hi Matt,
On Tue, Mar 23, 2010 at 3:25 PM, Matt McCutchen wrote:
> On Tue, 2010-03-23 at 15:05 -0700, Bruce Korb wrote:
>> Please forgive my digging up a two year old thread, but I've got the
>> same problem, but the pointers there give no help. This is using
>> version
Please forgive my digging up a two year old thread, but I've got the
same problem, but the pointers there give no help. This is using
versions 3.0.6 (server) and 3.0.7 (client).
Unfortunately, I have to type the client stuff in by hand. ("Secured"
laptop with highlighting & copying disabled.) A
