daemon-server via SSH (was Re: new rsync release needed soon?)

Dave Dykstra dwd at bell-labs.com
Fri Aug 30 19:28:02 EST 2002

On Thu, Aug 01, 2002 at 02:25:50PM -0500, Dave Dykstra wrote:
> I tried it out with an example like
>     rsync -e ssh --rsync-path=.... /etc/motd localhost::
> and the first thing one runs across is that the remote side tries to open
> /etc/motd.conf and reports an error only to the syslog.   The man page
> explains that the way to set a different config file is by using ssh
> and authorized_keys and set the forced command with a --config-file 
> option.  I suggest we have rsync --daemon first look for $HOME/rsyncd.conf
> before looking for /etc/rsyncd.conf.  That will be a modification to the
> server side, but other than that a cool thing about this patch is that it
> seems to work quite well with older versions of rsync on the server side.
> Also, I don't know how clean it will be to implement, but I think it will
> save us a lot of questions if we let that initial error message about not
> being able to open /etc/rsyncd.conf show up on the and the client and not
> go only to syslog.

I've submitted patches for the above to CVS.  Here's the checkin message:

    When using daemon mode over a remote shell program and not running as
    root, default the config file to just "rsyncd.conf" in the current
    directory instead of /etc/rsyncd.conf.  Also, fix problems with logging
    messages when running daemont mode over a remote shell program: it was
    pretty much doing the opposite of what it should have, sending early
    error messages to the log and later messages to the client.  Switched
    it around so the very early error messages go to the client and the
    later ones go to the log.
I think the man pages should still be updated to consistently talk change
what it used to call "rsync server" to "rsync server without a remote shell

- Dave Dykstra

More information about the rsync mailing list