I have 7 rsync mirrors set up, but I only see some clients hitting just
1 mirror even though the hostname resolves to 7 distinct IP addresses.
On a cent 4x box running rsync 2.6.9, I straced the rsync process, and
I can see the name resolution happen, and all 7 IP addresses are
returned, but
On Tue, Oct 07, 2008 at 05:03:44PM -0400, Hasenbalg Michael (JuP/TEF-MIS) wrote:
> In regards to one of the 'current issues and debugging' - Why does my
> transfer die with something like the following error? I found that this
> error occurs also if the path
> log file = /xyz/abc/rsyncd.log
> in y
Rsync version 3.0.5pre1 is now available for release testing. This is
a bug-fix release.
Please test this new release and send email to the rsync mailing list
with any questions, comments, or bug reports.
To see a full summary of the changes since 3.0.4, visit this link:
http://rsync.samba.or
On Fri, 2008-10-10 at 13:49 +0100, michael wrote:
> Although how do I start and restart it? I tried
> kill -HUP
> but that seems to have half killed it since now I can't restart:
> [EMAIL PROTECTED]:~$ ps -elf|grep rsyncd
> 0 R mkb 11929 11392 0 80 0 - 17433 - 13:48 pts/2
> 00:00:0
https://bugzilla.samba.org/show_bug.cgi?id=5804
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|RESOLVED|VERIFIED
--- Comment #2 from [EM
On Thu, Oct 09, 2008 at 06:44:20PM +0100, Giuliano Procida wrote:
> (Server) Protocol versions: remote=7680, negotiated=30
> protocol version mismatch -- is your shell clean?
This will be fixed in the next version. Until then, you can work around
the problem by supplying a "." after the "host:" a
https://bugzilla.samba.org/show_bug.cgi?id=5758
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=5804
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
Personally, and this is not something that any shell can solve, I
would love for a way to limit the files that the --server side rsync
allows access to.
I have an ssh command wrapper script, which I believe (and now just
hope) limits the access an SSH key provides to a user who uses this
key
