Issue with rsync server 2.5.7 on OpenBSD 3.4.

Stas stas at
Sat Apr 3 16:02:22 GMT 2004

Thank you for the tip - an inend.conf had a wrong path to rsyncd.conf
specified. /usr/bin instead of /usr/local/bin.
Now it works as it should.

But please tell me the following thing - if the transfers aren't protected
by ssh, basically, anyone can tamper with data being uploaded, by a backup
process, and that way render it's unusable, right?

And what the implications of running the rsync server with inetd over ssh,
over it's invocation with a remote rsync via ssh? In both the cases, the
rsync daemon is being dynamically loaded and unloaded, right? Maybe it's
just better to run it's with a rsync --daemon and not invoke it each time?

----- Original Message ----- 
From: "Wayne Davison" <wayned at>
To: "Stas" <stas at>
Cc: <rsync at>
Sent: Saturday, April 03, 2004 12:24 AM
Subject: Re: Issue with rsync server 2.5.7 on OpenBSD 3.4.

> On Sat, Apr 03, 2004 at 12:05:16AM +0200, Stas wrote:
> > rsync: connection unexpectedly closed (0 bytes read so far)
> Look in your syslog to see why the rsyncd is shutting down.  One
> possibility is that the permissions/ownership of the secrets file
> (if you're using one) is wrong.
> ..wayne..

More information about the rsync mailing list