Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Tue, 9 Oct 2001 12:56:41 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: "chmod a+x filename" shows no effect on W2K Message-ID: <20011009125641.B24952@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <3BC322CA.37D62AB0@cportcorp.com> <3BC342AA.11064.EE176@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3BC342AA.11064.EE176@localhost> User-Agent: Mutt/1.3.21i On Tue, Oct 09, 2001 at 06:32:10PM +0200, Gerrit P. Haase wrote: >> Peter Buckley schrieb am 2001-10-09 12:16: > >Set CYGWIN=tty andwhatyoulike >as systemwide environment variable so it is accessible by >all processes. > >>Also be aware that chmod may sporadically not work and >>then work. Just for no reason, and it isn't repeatable. > >Never seen such a behaviour. Me neither. AFAIK, we've had exactly one report of this behavior so I think it is premature to offer this as a general caveat to any use who uses CYGWIN=ntsec. I would suspect cockpit errors first. cgf -- 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/