This is the mail archive of the
mailing list for the Cygwin project.
Re: 1.7 - noacl for cygdrive
- From: Richard Ivarson <RiIvarson at gmail dot com>
- To: cygwin at cygwin dot com
- Date: Wed, 19 Nov 2008 20:51:28 +0100
- Subject: Re: 1.7 - noacl for cygdrive
- References: <002201c94993$3a4a2e50$aede8af0$@com> <20081118160333.GB12546@ednor.casa.cgf.cx>
Christopher Faylor schrieb:
On Tue, Nov 18, 2008 at 08:35:04AM -0700, Rob Bosch wrote:
Rob, many thanks for your reply.
So it's not just me having massive problems with the NT permissions which
being messed up by Cygwin tools like rsync. Actually most Cygwin users
all wrong after rsync resets them... Oh what a pity!
see these problems, I guess, because Windows 2000 and XP use NTFS.
I can't use rsync anymore, because the permissions of the destination are
Rsync will work fine with 1.5.25. Just set the global NTSEC (see
http://www.cygwin.com/cygwin-ug-net/ntsec.html). You have to set this
variable in your system environment so that any process spawned gets it,
especially if you are running rsync as a service. If you are scripting it,
add it in your cmd file.
ntsec is the *default* and has been for some time. There is no reason to set
Yes, Rob meant for us RSYNC users: set CYGWIN=NONTSEC
... because NTSEC (the default) causes much trouble with the NT permissions
on RSYNC'ed files. A web search shows that _many_ people run into these
problems. So maybe for RSYNC the default NTSEC isn't a good idea. I'm on edge
how Cygwin 1.7 solves or rather handles this problem.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html