You da boss.
And thanks for looking into this, it'll save other folks heartache in
the future.
Scott
Dave Dykstra wrote:
>On Tue, Jun 25, 2002 at 05:11:40PM -0400, pyxl wrote:
>
>>Well,
>>
>>Looking at the source for 2.5.5, I'm only seeing mention of it
r --owner (-o) and --group (-g) client side options to function,
+"use chroot" must be set to false for the module\&. The
default for "use chroot" is true\&.
.IP
.IP "\fBmax connections\fP"
I'll attach it as a file as well.
Scott
On Mon, Jun 24,
Well, it's definitely not in either of the man pages - and those should
be the canonical documentation of rsync's behavior. But it's a small
bug (with big teeth!).
Corey Stup wrote:
> pyxl wrote:
>
>> Hi all,
>>
>> Tripped over a documentation bug. I
Hi all,
Tripped over a documentation bug. I'm guessing the behavior I've found
isn't a bug in itself as it's kind of implied by chroot (unless the
/etc/passwd db is read *before* you do the chroot call), so I'm calling
it a documentation bug.
The Setup:
System A: running rsync --daemon fro
As Dave noted in a response to an earlier message with his statement
that he's updated the documentation to note the unidirectional behavior
of exclude filtering, my saying that the exclude behavior with --delete
is a bug is definitely wrong. The behavior is (wisely) designed in.
Just wante
Dave Dykstra wrote:
>On Fri, May 10, 2002 at 05:19:47PM -0400, pyxl wrote:
>
>>Hello all,
>>
>>I've found some behavior in 2.5.5 that is contrary to the documentation
>>in the man page.
>>
>>Specifically, I'm running an rsync server
And, I've found more.
It turns out that even though the exclude directive is ignored for
inbound data in rsyncd.conf, it is NOT ignored for the --delete option.
I've seen this behavior occur when I've deleted a file from the sending
side (client) that is inside a tree that's matched by the se
Hi folks, me again.
I'm writing this primarily so that it will get posted to a listserve
archive and snarfed up by Google for future people's note.
When using the exclude directive in rsyncd.conf (i.e. using rsync from
inetd), I've found that it appears to be implemented to operate in one
dat
And today is apparently my day to put *both* feet in my mouth concurrently.
The behavior is still being evinced on the server side, even with a
correctly syntaxed exclude line.
*sigh*
Oh well. At this point, I'm going to stop posting to the list about this.
--
To unsubscribe or change opti
Please ignore that email. I just realized my error - missing the all
important = on the line.
DUH.
*shakes head*
Sorry folks.
Scott
--
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Hello all,
I've found some behavior in 2.5.5 that is contrary to the documentation
in the man page.
Specifically, I'm running an rsync server (i.e. from inetd with
--daemon),and in the module definition I'm specifying the line "exclude
nosyncdir". The documentation for rsyncd.conf indicates
Howdy everybody,
Dunno if anyone's got a log monitor or mailing script set up for 404
errors on rsync.samba.org, but
http://rsync.samba.org/rsync/fom-serve/cache/1.html
emits a 404. It's where the the FAQ-O-Matic nav link that's found
throughout the site eventually sends the browser.
Sorry ab
12 matches
Mail list logo
