On Sun, Jun 20, 2004 at 01:56:05PM +0200, BASING Denis Zvegelj wrote:
> I can tell you that the fact is that rsync daemon does not even work
> on kernel 2.4.25, neither 2.4.25
Did you use the -4 option as suggested? That should allow rsync to
start on older kernels that don't support IPv6 quite r
I'm not a programmer, so I can't really argue to your comments, but I can
tell you that the fact is that rsync daemon does not even work on kernel
2.4.25, neither 2.4.25, and I'm not able to upgrade to higher kernle until
acl patch is available, so my only option is to downgrade rsync to 2.5.7, to
On Wed, May 05, 2004 at 10:02:41AM +0200, Paul Slootman wrote:
> If that's the root cause of the problem, skipping the IPV6 socket when
> that call fails should suffice.
I've decided against using this change as I think it would prevent some
older Linux (any other?) systems from accepting IPv6 con
On Wed 05 May 2004, Jan-Benedict Glaw wrote:
>
> Runtime check? Right. Think about distributions that offer both 2.4.x
> and 2.6.x. For sure you won't like to deliver two rsync versions to your
> users:) ...and because IPV6_V6ONLY exists in 2.4.21 upwards, I think
> that's not a major problem. Hey
On Wed, 2004-05-05 at 15:49, Jan-Benedict Glaw wrote:
> On Wed, 2004-05-05 14:44:49 -0400, Gregory Symons <[EMAIL PROTECTED]>
[snip]
> > And I am indeed running a 2.4.20 kernel. So maybe the configure script
> > needs to detect whether or not this flag is actually available (which I
> > thought was
On Wed, 2004-05-05 14:44:49 -0400, Gregory Symons <[EMAIL PROTECTED]>
wrote in message <[EMAIL PROTECTED]>:
> On Wed, 2004-05-05 at 04:02, Paul Slootman wrote:
> But in Linux, IPV6_V6ONLY socket option does not exist in kernel2.4.20
> or earlier, except for USAGI kernels. Therefore, you can't do a
On Wed, 2004-05-05 at 04:02, Paul Slootman wrote:
[snip]
> > I haven't really done any network programming, so I'm not exactly sure what's
> > going on
> > in this section of the code, but it looks like rsync tries to set a flag on the
> > IPV6
> > socket indicating that its only to be used for I
On Tue, May 04, 2004 at 09:25:17PM +0200, Martin Kjeldsen wrote:
> 2004/05/04 21:15:10 [22369] rsyncd version 2.6.2 starting, listening on port 873
> 2004/05/04 21:15:10 [22369] rsync error: error in socket IO (code 10) at
> socket.c(466)
Rsync 2.6.2 now tries to listen on multiple interfaces, e.
On Tue 04 May 2004, Gregory Symons wrote:
>
> I've got the exact same problem here. For me at least,it appears that rsync is
> trying to bind to the same address twice. Below is an excerpt from
> 'strace rsync --daemon':
[snip]
>
> I haven't really done any network programming, so I'm not exact
Martin Kjeldsen said:
> Hi,
>
> I've a problem with rsync 2.6.2 and the daemon. I've installed it precisly
> as I did with 2.6.0 (I've tried before with 2.6.1 and was having the same
> problems as now with 2.6.2).
>
> When I try to a rsync --daemon command the rsync offcourse finishes, but in
> t
Hi,
I've a problem with rsync 2.6.2 and the daemon. I've installed it precisly
as I did with 2.6.0 (I've tried before with 2.6.1 and was having the same
problems as now with 2.6.2).
When I try to a rsync --daemon command the rsync offcourse finishes, but in
the log file it says
2004/05/04 21:15
11 matches
Mail list logo
