rsync - Jan 2006 - cwrsync server 2.0.4 / winxp / ownership problems?

Hi all!

We're using cwrsync server 2.0.4 on winxp to keep files up to date between
some operator machines.

Whenever I run rsync to send files to another machine, the read-only flag
gets set.  The cwrsync user was created (the install is completely
standard)... so I'm thinking it might have something to do with that.

Here's my rsyncd.conf:

use chroot = false
strict modes = false
hosts allow = *
log file = rsyncd.log
pid file = rsyncd.pid

[crystal_windows]
path=/stuff/windows
read only=false
comment=some stuff

When I run the following command from my laptop:
rsync -vzrLpogtu /stuff/windows/ user@node7::crystal_windows

It sets *ALL* the files in the /stuff/windows folder on the remote machine
to read-only.

This is a big problem because it means that when an operator goes to edit a
file in the windows folder with a program, he has to first make the file not
read only.

Is it possible to change the cwrsync configuration so that it runs as the
same user that the operator logs in as?  I'm thinking that for some reason
windows is getting confused and setting the ownership to the cwrsync user
and that's why the operator user sees the file as read-only.  Because the
operator is an administrator, the read-only can be turned off, but every
time rsync touches the folder it seems to reset all the permissions
settings.

Thanks in advance!

Hi Erik,

Since cwrsync contains some windows-specific arrangements not directly related
to rsync itself, I've
established a cwrsync discussion forum half a year ago. It is available at
http://www.itefix.no/phpws/index.php?module=phpwsbb&PHPWSBB_MAN_OP=viewforum&PHPWS_MAN_ITEMS=1
. You
may consider to post your problem at this forum as well.

Back to your problem: By default, cwrsync is configured to not to map unix
permissions to windows
equivalents (env.variable CYGWIN=nontsec). In other words, what you set as
windows permissions on
your directories will not be disturbed by cwrsync. If you want to give your
admins write permissions
on /stuff/windows, you may simply run the command below only once:

Xcacls "windows directory behind module crystal_windows" /T /E /G
Administrators:F

Best regards

Tev

cwRsync maintainer

http://itefix.no/cwrsync
http://sourceforge.net/projects/sereds 
> -----Original Message-----
> From: rsync-bounces+tevfik=itefix.no@lists.samba.org 
> [mailto:rsync-bounces+tevfik=itefix.no@lists.samba.org] On 
> Behalf Of Erik Jacobs
> Sent: 30. januar 2006 22:25
> To: rsync@lists.samba.org
> Subject: cwrsync server 2.0.4 / winxp / ownership problems?
> 
> Hi all!
> 
> We're using cwrsync server 2.0.4 on winxp to keep files up to 
> date between some operator machines.
> 
> Whenever I run rsync to send files to another machine, the 
> read-only flag gets set.  The cwrsync user was created (the 
> install is completely standard)... so I'm thinking it might 
> have something to do with that.
> 
> Here's my rsyncd.conf:
> 
> use chroot = false
> strict modes = false
> hosts allow = *
> log file = rsyncd.log
> pid file = rsyncd.pid
> 
> [crystal_windows]
> path=/stuff/windows
> read only=false
> comment=some stuff
> 
> When I run the following command from my laptop:
> rsync -vzrLpogtu /stuff/windows/ user@node7::crystal_windows
> 
> It sets *ALL* the files in the /stuff/windows folder on the 
> remote machine to read-only.
> 
> This is a big problem because it means that when an operator 
> goes to edit a file in the windows folder with a program, he 
> has to first make the file not read only.
> 
> Is it possible to change the cwrsync configuration so that it 
> runs as the same user that the operator logs in as?  I'm 
> thinking that for some reason windows is getting confused and 
> setting the ownership to the cwrsync user and that's why the 
> operator user sees the file as read-only.  Because the 
> operator is an administrator, the read-only can be turned 
> off, but every time rsync touches the folder it seems to 
> reset all the permissions settings.
> 
> Thanks in advance!
> 
> --
> To unsubscribe or change options: 
> https://lists.samba.org/mailman/listinfo/rsync
> Before posting, read: 
> http://www.catb.org/~esr/faqs/smart-questions.html
>

On Mon, Jan 30, 2006 at 04:25:01PM -0500, Erik Jacobs
wrote:
> Whenever I run rsync to send files to another machine, the read-only
> flag gets set.
The version of rsync in CVS has an option named --chmod that lets you
request permission changes for the copied files, so using that as the
client version for the copy would allow you to specify "--chmod=o+w"
to
ensure that write permissions were enabled for the owner.  It also has
new daemon options that allow chmod changes to be made to files coming
to and going from a daemon module: "incoming chmod" &
"outgoing chmod".
This would allow you to specify "outgoing chmod = o+w" in the
module's
config and upgrade just the rsync used by the daemon (the client rsyncs
wouldn't need to know about the --chmod option in this scenario).

..wayne..