delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2003/05/21/15:08:07

Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Wed, 21 May 2003 12:07:51 -0700 (PDT)
From: Brian Slesinsky <bslesins AT best DOT com>
X-X-Sender: bslesins AT bslesins DOT best DOT vwh DOT net
To: cygwin AT cygwin DOT com
Subject: Re: ownership of files created using cygwin
In-Reply-To: <Pine.GSO.4.44.0305211442190.26639-100000@slinky.cs.nyu.edu>
Message-ID: <Pine.BSF.4.40.0305211155450.725-100000@bslesins.best.vwh.net>
MIME-Version: 1.0

Thanks.  Adding "nontsec" to CYGWIN restores the old behavior for
permission inheritance.

A doc suggestion: I did happen across the ntsec page in the user manual
before posting, and I see now that it does mention the "ntsec" option, but
it is easily missed and perhaps this could be made a little more
prominent.  (Have a section on configuration with a link to the CYGWIN
options page.)

Also, I see that even the old behavior doesn't mimick Windows exactly:
the file owner isn't "Administrator".  But it's good enough.

- Brian


--
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/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019