X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=0.0 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD
X-Spam-Check-By:	sourceware.org
From:	John Ruckstuhl <john_ruckstuhl AT hansenmedical DOT com>
To:	"cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Date:	Wed, 14 Sep 2011 15:14:01 -0700
Subject:	RE: cygwin 1.7.9, problem with cygwin1.dll, path_conv::check, has_acls()? (Windows 7)
Message-ID:	<3ED156B391DFFE4685AD2AEA0159D28004E91D8DE3@USWINHQMBX1.hansenmedical.com>
References:	<3ED156B391DFFE4685AD2AEA0159D28004E91D8C79 AT USWINHQMBX1 DOT hansenmedical DOT com> <j4qpsh$b3q$1 AT dough DOT gmane DOT org> <4E70EC5B DOT 50209 AT cygwin DOT com> <3ED156B391DFFE4685AD2AEA0159D28004E91D8DA5 AT USWINHQMBX1 DOT hansenmedical DOT com> <4E7113EB DOT 9040407 AT cygwin DOT com>
In-Reply-To:	<4E7113EB.9040407@cygwin.com>
MIME-Version:	1.0
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id p8EMELoD013738

Larry Hall wrote:
>On 9/14/2011 4:31 PM, John Ruckstuhl wrote:
>> Larry Hall wrote:
>>> On 9/14/2011 1:56 PM, Thorsten Kampe wrote:
>>>> The obvious way to troubleshoot this would be to use a network drive (Z:
>>>> for instance) instead of UNC or to mount the share and see if that
>>>> works. Naturally it would also make sense to test the latest Cygwin
>>>> snapshot and to see if you get the same result if you use //localhost/C
>>>> $.
>>>
>>> Right.  I was thinking this could fall into the category of a network
>>> share that needs to have the "noacl" mount option set.  So another
>>> option is to try mounting the UNC path to a Cygwin path (in /etc/fstab)
>>> and specify the "noacl" option.

>> It seems you are suspicious of the mount... that a defective mount WOULD
>> interfere when the target is expressed one way, and WOULDNOT interfere
>> when the target is expressed the other way.
>
> Not defective, no.  In my case, I'm suggesting that you turn off POSIX
> permissions.  These sometimes cause problems for network drives.  So
> do something like this:
>    mkdir /foo
>    mount -o noacl,binary,notexec //hyperdisk/Data/Engineering/ruck /foo
> Then try the same tests using /foo as the root path.

Okay, Larry's thinking is confirmed.
    $ mkdir /foo.noacl
    $ mount -o noacl,binary,notexec //hyperdisk/Data/Engineering/ruck /foo.noacl
    $ mkdir /foo.acl
    $ mount -o binary,notexec //hyperdisk/Data/Engineering/ruck /foo.acl
    $ cd /foo.noacl
    $ touch xoo.1
    $ cd /foo.acl
    $ touch xoo.2
    touch: cannot touch `xoo.2': Permission denied
That is, problem shows under /foo.acl (but not under /foo.noacl)

But for what it's worth, my problem does NOT appear when I'm on a 1.7.7
System hitting that same fileserver-directory.

The system WITHOUT the problem is 
    Windows XP SP3, and uname -a says:
    CYGWIN_NT-5.1 HZ4X1C1 1.7.7(0,230/5/3) 2010-08-31 09:58 i686 Cygwin
The system WITH the problem is 
    Windows 7 SP1, and uname -a says:
    CYGWIN_NT-6.1 CND0360JCB 1.7.9(0.237/5/3) 2011-03-29 10:10 i686 Cygwin

I don't know if the differing behavior is due to different Cygwin or due
to different OS.
Also, thanks for the link to using-utils.html#mount !

Thanks,
John

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

- Raw text -