DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:subject:to:content-type;
	 q=dns; s=default; b=oiOZw04F1zsLUS+2hmPx7AsEvQ8apEcNPbABch5R9SS
	j4L4pj6fJlMikGWtDBUWCNwZbrlay6FbIBdTRTKYJ+F2RmF2uW+plWuhv5onkQjh
	rcwP8sUTWdhLGW0ikIs9hUFOB0u2rxAw0k9H2Wdfn+bTzysWc02t0kFpdlsPzUV8
	=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-ID: <5c1f242b.1c69fb81.2721c.076d@mx.google.com>
Date: Sat, 22 Dec 2018 21:59:07 -0800 (PST)
From: Steven Penny <svnpenn AT gmail DOT com>
Subject: "test" producing unexpected results after "chmod"
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=utf8; format=flowed
User-Agent: Tryst/2.8.0 (cup.github.io/umber/awk/tryst)

With Linux, these commands produce expected results:

    $ cd /tmp
    $ touch alpha.txt
    $ test -r alpha.txt; echo "$?"
    0
    $ chmod -r alpha.txt
    $ test -r alpha.txt; echo "$?"
    1
    $ chmod +r alpha.txt
    $ test -r alpha.txt; echo "$?"
    0

However with Cygwin, unexpected results are produced:

    $ cd /tmp
    $ touch alpha.txt
    $ test -r alpha.txt; echo "$?"
    0
    $ chmod -r alpha.txt
    $ test -r alpha.txt; echo "$?"
    0

It seems Cygwin is not able to produce non-readable files.


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