Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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, 7 Aug 2002 11:42:01 +0200 From: Corinna Vinschen To: cygwin Subject: Re: Win2k owner and Administrators Message-ID: <20020807114201.W3921@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin References: <20020806215223 DOT 17028 DOT qmail AT web21409 DOT mail DOT yahoo DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020806215223.17028.qmail@web21409.mail.yahoo.com> User-Agent: Mutt/1.3.22.1i On Tue, Aug 06, 2002 at 02:52:23PM -0700, Noel Yap wrote: > Does anyone know how to solve or workaround when, > being in the group Administrators, one creates a file > from a non-Cygwin program, the file is owned by > Administrators. Such ownership can cause problems > when, for example, umask is set to 027 (as I do), > making these newly created files and directories > read-only to me even though I was the one who created > them. I don't know if that's already available on W2K but at least on XP: Open the appropriate "Security Policy" MMC snap-in. In the object tree on the left side search for the "Security Options" object. In the list window on the right side you'll find a setting "System objects: Default owner for objects created by members of the Administrators group". This knows two settings, "Administrators group" and "Object creator". Perhaps you'll have to reboot. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/