This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: 1.7 - noacl for cygdrive


On Nov 19 20:51, Richard Ivarson wrote:
> 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
>>> are
>>>> being messed up by Cygwin tools like rsync. Actually most Cygwin users
>>> should
>>>> 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
>>> all wrong after rsync resets them... Oh what a pity!
>>>
>>> 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
>> it.
>
> 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.

For rsync ntsec is a good idea, imho.  Your scenario isn't my scenario.
I *want* permissions which reflect POSIX permissions closely.  I don't
care for Windows default permissions.  Lately we have lots of people
claiming that they use Cygwin tools in a native Windows environment and
how being POSIXy is in the way of what they are doing.  Keep in mind
that the whole idea of Cygwin is to provide a POSIXy environment and the
default should be as close to POSIX as possible.  Using Cygwin in a
non-POSIXy situation is the border case, not the norm.  So adapt your
settings, but don't expect that it's the default.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]