cwrsync server 2.0.4 / winxp / ownership problems?
erik.jacobs at crystalcc.com
Tue Jan 31 12:26:46 GMT 2006
Thanks for the pointer. I may move this over to cwRsync just to keep a good
record of it in multiple places.
I don't care about porting the permissions over from/to *nix -- I have a
cron that resets the perms on the folder structure on the *nix machines (QNX
6.3 if you're interested). The real problem is that when an operator makes
a change on UI1 and runs the sync batch file, all the other UIs end up with
If I run that command on the folder /stuff will all of the subfolders
inherit those permissions?
Thanks for your help again.
From: Tevfik Karagülle [mailto:tevfik at itefix.no]
Sent: Monday, January 30, 2006 5:35 PM
To: 'Erik Jacobs'
Cc: rsync at lists.samba.org
Subject: RE: cwrsync server 2.0.4 / winxp / ownership problems?
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
&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
> -----Original Message-----
> From: rsync-bounces+tevfik=itefix.no at lists.samba.org
> [mailto:rsync-bounces+tevfik=itefix.no at lists.samba.org] On
> Behalf Of Erik Jacobs
> Sent: 30. januar 2006 22:25
> To: rsync at 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
> read only=false
> comment=some stuff
> When I run the following command from my laptop:
> rsync -vzrLpogtu /stuff/windows/ user at 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:
> Before posting, read:
More information about the rsync