Help understanding rsync and cwrsync

Peter petermatulis at
Thu Mar 2 04:22:12 GMT 2006

--- Doug Lochart <dlochart at> wrote:

> Ok, how does cwrsync handle ACLs, users and
> permissions as on the
> windows box?  How/where is that info kept in the
> filesystem on the
> linux box?  Is it in meta-data?  I figure basic file
> permissions are
> stored with the file but how is the user stored?  I
> can't imagine we
> would have to create a user account for that end
> user ... or would we?

I can get back to you later on this important
question.  I like to hear what others on this list are
saying on this point.

> > The config file containing the module settings is
> read
> > by rsync at every connection so you do not need to
> > restart the daemon.  Alternatively, you can run
> rsyncd
> > on a single-transfer basis.  The remote user
> invokes
> > the daemon.
> Could you explain how the last part works?  (the
> remote user invokes
> the daemon)?
> Most examples I have seen mention running it in
> daemon mode or via inetd?

On Windows box user invokes like this assuming src
directory is on D: drive,

rsync.exe -avr --rsh=ssh /cygdrive/d/<src dir> <remote

--rsh is to specify encryption (optional).  If you
instead contact a standalone or inetd-awoken daemon
then encryption is performed by default.

The key for "remote user invokes the daemon" is the
double colon followed by a module name.  The user then
supplies local password just as if he's logging in via
SSH.  In such case, single-transfer daemon is brought
up and he checks user home directory for instructions
(rsyncd.conf).  To avoid a second (rsync)
authentication do not use 'auth users' line in that
file.  This way each user has their own configuration.

Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 

More information about the rsync mailing list