X-Spam-Check-By: sourceware.org
Date: Wed, 25 Oct 2006 11:05:34 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: 1.5.21-1: CIFS symlinks on network share break Cygwin
Message-ID: <20061025090534.GA7791@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20061024102745 DOT GV8323 AT calimero DOT vinschen DOT de> <E173C70E3D81F74188D2778B96C5CD0D7FFC91 AT postal1-dog DOT naughtydog DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <E173C70E3D81F74188D2778B96C5CD0D7FFC91@postal1-dog.naughtydog.com>
User-Agent: Mutt/1.4.2i
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

On Oct 24 11:08, Jonathan Lanier wrote:
> One completely wild guess would be that there is some attribute
> associated with the process that might expose the native symlinks,
> possibly for improved compatibility with SFU/Posix and CIFS;

Cygwin processes are ordinary Win32 processes, just linked against
cygwin1.dll.  When calling GetFileAttibutes, it's the same function from
kernel32 as a non-Cygwin process calls.

> However, as I said, I double-checked the PE headers and
> the application type is definitely not marked as Posix.

Of course not.  Cygwin is a POSIX emulation in the win32 namespace, it's
not a POSIX subsystem.

>  maybe internally Cygwin is forking a
> process that is inheriting some undesired Posix attribute?

I'm not aware that such a flag would exist.  Your example takes forking
out of the picture anyway since that doesn't happen when starting your
testcase from a cmd.exe prompt.

If at all, it has something to do with opening files.  Still, the effect
is not reproducible with Samba shares.  Samba has the capability to
support CIFS clients with CIFS UNIX extensions.  This capability is
switched on by default.  Nevertheless, Cygwin application on a Windows
client don't see anything of this.  They see the same as any native
Windows application.  Cygwin does not implement it's own SMB/CIFS file
access, it just uses Win32 resp. NT system calls.  That's why I think
that the CIFS server is getting something wrong here.  Before debugging
Cygwin to death, it would be interesting to learn the cause on the side
of the CIFS server.  I assume there's something like logfiles or some
sort of support for this CIFS server?


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

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