X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=0.6 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 13:31:50 -0700
Subject: RE: cygwin 1.7.9, problem with cygwin1.dll, path_conv::check, has_acls()?  (Windows 7)
Message-ID: <3ED156B391DFFE4685AD2AEA0159D28004E91D8DA5@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>
In-Reply-To: <4E70EC5B.50209@cygwin.com>
Content-Type: text/plain; charset="us-ascii"
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
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id p8EKWCQT006501

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.

------------------------------------------------------------------------
Both of your comments are a bit over my head.  
I'll put in an honest effort to figure out what you mean, and then reply 
with results.
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.

Meanwhile -- hopefully my presentation was clear... 
When I use only forward slashes THEN I get bad permissions and fail.
    Bad:   touch ./zoo.4
    Bad:   touch //hyperdisk/Data/Engineering/ruck/zoo.6
If I refer to the target with at least some backslash in the path, all is good.
    Good:  touch .\\zoo.5
    Good:  touch //hyperdisk/Data/Engineering/ruck\\zoo.7

And from the straces, line 202 differs -- the "Bad" case is using 
normalize_posix_path, the "Good" case is using normalize_win32_path.

------------------------------------------------------------------------
strace.out (fail case, touch $(pwd)/zoo.6)
------------------------------------------------------------------------
   201     44   33624 [main] touch 6444 normalize_posix_path: src //hyperdisk/Data/Engineering/ruck/zoo.6
   202     40   33664 [main] touch 6444 normalize_posix_path: //hyperdisk/Data/Engineering/ruck/zoo.6 = normalize_posix_path (//hyperdisk/Data/Engineering/ruck/zoo.6)
   203     49   33713 [main] touch 6444 mount_info::conv_to_win32_path: conv_to_win32_path (//hyperdisk/Data/Engineering/ruck/zoo.6)


------------------------------------------------------------------------
strace.7.out (success case, touch $(pwd)\\zoo.7)
------------------------------------------------------------------------
   201     38   35785 [main] touch 6840 normalize_posix_path: src //hyperdisk/Data/Engineering/ruck\zoo.7
   202     39   35824 [main] touch 6840 normalize_win32_path: \\hyperdisk\Data\Engineering\ruck\zoo.7 = normalize_win32_path (//hyperdisk/Data/Engineering/ruck\zoo.7)
   203     39   35863 [main] touch 6840 mount_info::conv_to_win32_path: conv_to_win32_path (//hyperdisk/Data/Engineering/ruck/zoo.7)

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