On Thu, Jun 03, 2004 at 09:43:48AM -0400, John Taylor wrote:
> I think rsync should also check $SSH_CONNECTION. This shows up in
> newer versions of ssh/sshd.
Thanks for the nudge. I googled the ssh project and it appears that
SSH_CLIENT is now deprecated, so SSH_CONNECTION is the preferred
vari
On Thu, Jun 03, 2004 at 12:30:53AM -0700, Wayne Davison wrote:
> On Fri, May 28, 2004 at 09:05:42AM -0700, Bill Moseley wrote:
> > I just setup rsync on Solaris 2.6 and my log file shows:
> > 2004/05/28 07:54:03 [20996] rsync allowed access on module foo from 0.0.0.0
> > (0.0.0.0)
>
> This messag
On Thu, Jun 03, 2004 at 12:30:53AM -0700, Wayne Davison wrote:
> On Fri, May 28, 2004 at 09:05:42AM -0700, Bill Moseley wrote:
> > I just setup rsync on Solaris 2.6 and my log file shows:
> > 2004/05/28 07:54:03 [20996] rsync allowed access on module foo from 0.0.0.0
> > (0.0.0.0)
>
> This messag
On Fri, May 28, 2004 at 09:05:42AM -0700, Bill Moseley wrote:
> I just setup rsync on Solaris 2.6 and my log file shows:
> 2004/05/28 07:54:03 [20996] rsync allowed access on module foo from 0.0.0.0 (0.0.0.0)
This message is only output if you're running a daemon rsync over a
remote shell connecti
I just setup rsync on Solaris 2.6 and my log file shows:
2004/05/28 07:54:03 [20996] rsync allowed access on module foo from 0.0.0.0 (0.0.0.0)
instead of the actual connecting IP address. Is this a config issue?
I don't know if this is related but when building:
socket.c: In function `try_bind
