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 Message-ID: <3500515B75D9D311948800508BA379559506C3@EX-LONDON> From: Vince Hoffman To: "'Volker Quetschke'" , cygwin AT cygwin DOT com Subject: RE: chmod problem Date: Mon, 9 Sep 2002 10:45:03 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" i seem to remember windows permission inheritance can cause this kind of problem ? maybe have a search of the archives, but its still monday morning so my brain may not be working properly yet. -----Original Message----- From: Volker Quetschke [mailto:quetschke AT scytek DOT de] Sent: 08 September 2002 18:53 To: cygwin AT cygwin DOT com Subject: Re: chmod problem Hi! > -> Err, in which FAQ is this written? Just try chmod, it works! >>From the FAQ: > > Why doesn't chmod work? > `ntsec' will allow UNIX permissions in Windows NT on NTFS file systems. Yes, you have to have ntsec or ntea set in your CYGWIN environement variable to be able to use chmod. > -> As I said, use chmod. I am using gnupg on a win2k system. > > I tried using chmod. Although I get no errors and in verbose mode it says > the permissions are changed, a "ls -al" shows: > > $ chmod 600 * > > perry AT ELVIS ~/.gnupg > $ ls -la > total 235 > drwxr-xr-x 2 perry None 4096 Sep 8 09:46 . > drwxr-xr-x 7 perry None 8192 Sep 8 11:58 .. > -rw-r--r-- 1 perry None 7793 Sep 8 09:41 options It seems you don't have ntsec or ntea set in your CYGWIN variable. As a workaround you can always use the keyword no-permission-warning in your gnupg options file, but I think the proper way is to use CYGWIN=ntsec (plus your other options). Bye Volker -- PGP/GPG key (ID: 0x9F8A785D) available from wwwkeys.de.pgp.net key-fingerprint 550D F17E B082 A3E9 F913 9E53 3D35 C9BA 9F8A 785D -- 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/