Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Date:	Thu, 12 Aug 2004 08:44:36 +1200
From:	Stuart Rackham <srackham AT methods DOT co DOT nz>
Subject:	1.5.10: Shebangs not detected from mounted network drive
To:	cygwin AT cygwin DOT com
Message-id:	<411A8534.4030705@methods.co.nz>
MIME-version:	1.0
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040616
X-IsSubscribed:	yes

Hi

When a script is accessed through the network drive path name
(/h/tmp/test-script) the shebang is detected and the file mode is seen
as executable, but when the same file is accessed through the mount
path (/home/srackham/tmp/test-script) or a relative path it is not detected.

Can anyone shed any light on this behavior (I searched but didn't come 
up with anything), is there a configuration option I'm missing? or is
it a known feature or a known bug?

For example I have a network drive (Samba 3.0.0 server) mounted to my
local home directory:

H:\tmp         /home/srackham/tmp       system  binmode

To replicate the problem create a script and view the file
permissions:

   $ cd /h/tmp
   $ cat >test-script
   #!/bin/sh
   echo Hello World!
   ^D

   $ ls -l test-script ../tmp/test-script \
   > /home/srackham/tmp/test-script /h/tmp/test-script

   -rw-r--r--    1 srackham None   34 Aug 11 16:22 ../tmp/test-script
   -rwxr-xr-x    1 srackham None   34 Aug 11 16:22 /h/tmp/test-script
   -rw-r--r--    1 srackham None   34 Aug 11 16:22 
/home/srackham/tmp/test-script
   -rw-r--r--    1 srackham None   34 Aug 11 16:22 test-script

The same file is seen as simultaneously having and not having execute
permission. Shebang searching seems to stop when a network drive is
encountered in the mount path.

The script still executes correctly through the mount path but the
bash command-line completion does not nor is the execute bit seen:

   $ /home/srackham/tmp/test-script
   Hello World!

Here's some environment information:

Windows XP Professional Ver 5.1 Build 2600 Service Pack 1

c:  hd  FAT32  32749Mb  96% CP    UN
h:  net NTFS   29525Mb  80% CP CS    PA        srackham

C:\cygwin      /                        system  binmode
H:\tmp         /home/srackham/tmp       system  binmode
C:\cygwin/bin  /usr/bin                 system  binmode
C:\cygwin/lib  /usr/lib                 system  binmode
.              /                        system  binmode,cygdrive

Cygwin DLL version info:
   DLL version: 1.5.10
   DLL epoch: 19
   DLL bad signal mask: 19005
   DLL old termios: 5
   DLL malloc env: 28
   API major: 0
   API minor: 116
   Shared data: 4
   DLL identifier: cygwin1
   Mount registry: 2
   Cygnus registry name: Cygnus Solutions
   Cygwin registry name: Cygwin
   Program options name: Program Options
   Cygwin mount registry name: mounts v2
   Cygdrive flags: cygdrive flags
   Cygdrive prefix: cygdrive prefix
   Cygdrive default prefix:
   Build date: Tue May 25 22:07:00 EDT 2004
   CVS tag: cr-0x5e6
   Shared id: cygwin1S4


Cheers, Stuart
-- 
Stuart Rackham

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

- Raw text -