Rob,
Actually, this behavior also depends on the filesystem you use.
CYGWIN=ntsec alone only helps if you have NTFS. For FAT you also need
"ntea" (i.e., CYGWIN="ntsec ntea" -- be aware that it'll create a large
file in your drive's root directory). I believe permissions on FAT32 were
broken some
Thank you Elfyn and Jurgen. A few moment's thought would have reminded
me that file permissions are handled differently on NT. ;)
Regards
Rob
Elfyn McBratney wrote:
Rob Clack wrote:
[...]
So there seems to be a couple of weensy buggettes there, though I'm not
suggesting anyone bother to fix t
Rob Clack wrote:
> [...]
> So there seems to be a couple of weensy buggettes there, though I'm not
> suggesting anyone bother to fix them unless they happen to be working
> there anyway. They're not serious bugs, but they did obscure the real
> problem and waste quite a lot of my and several o
[EMAIL PROTECTED]
08/29/2003 12:33 PM
To: [EMAIL PROTECTED]
cc: (bcc: Jurgen Defurne/BRG/CE/PHILIPS)
Subject: Re: [Fwd: Re: perl test fails]
Classification:
Hooray, we're there! Thank you!
The -x operator works perfectly, but the pro
Hooray, we're there! Thank you!
The -x operator works perfectly, but the problem was still rather
obscure, so here's the answer.
Cygwin 1.3.22-1 under NT4, Perl 5.8.0
My script was almost identical to the one Elfyn supplied below, it just
tested a local file rather than /usr/bin/perl.
#!/bin
Rob Clack wrote:
> Well I thought maybe I'd better just try setting $CYGWIN, even though it
> didn't seem relevant (I don't have "..problems with NT shares or Samba
> drives..", since the script reliably breaks when run from a local,
> non-shared drive) and indeed, it made no difference. Unles
Well I thought maybe I'd better just try setting $CYGWIN, even though it
didn't seem relevant (I don't have "..problems with NT shares or Samba
drives..", since the script reliably breaks when run from a local,
non-shared drive) and indeed, it made no difference. Unless there's
some special w
Thank you Igor. However, I've now read the entry on smbntsec and it
doesn't seem relevant. (Was a useful exercise in itself, since I didn't
know about the CYGWIN env var either ;)) I don't have a problem on the
Linux box, only on the NT one. And it doesn't matter whether I'm running
the scrip
On Wed, 27 Aug 2003, Rob Clack wrote:
> Hmmm, don't see how it can have anything to do with the mapping of a
> networked drive, since the problem started on the NT4 box, at which time
> the scriptlet was located in /cygdrive/e/cygwin/rnc/try.
>
> Since I wanted to demonstrate that it worked on the
Hmmm, don't see how it can have anything to do with the mapping of a
networked drive, since the problem started on the NT4 box, at which time
the scriptlet was located in /cygdrive/e/cygwin/rnc/try.
Since I wanted to demonstrate that it worked on the Linux box (having
tripped over that one orig
At 09:36 AM 8/26/2003, Rob Clack you wrote:
>Gerrit
>
>I've been away for a week, hence the delayed response.
>
>Thanks for this and clearly my scriptlet was broken. I've now tried both
>alternatives as suggested below. Both work perfectly under Linux. Neither works
>under NT4.
>
>Linux output
Gerrit
I've been away for a week, hence the delayed response.
Thanks for this and clearly my scriptlet was broken. I've now tried
both alternatives as suggested below. Both work perfectly under Linux.
Neither works under NT4.
Linux output:
script is executable
NT4 output:
I damn well am!
Hallo Rob,
Am Freitag, 15. August 2003 um 11:59 schriebst du:
> Not sure if this is the right list for my question.
> cygwin 1.3.22-1 running under NT4.
> I have a perl script that runs an executable, so before actually running
> it, the code checks that the file exists and is executable, but
Not sure if this is the right list for my question.
cygwin 1.3.22-1 running under NT4.
I have a perl script that runs an executable, so before actually running
it, the code checks that the file exists and is executable, but the test
fails under cygwin. Under linux and OSF1 it's fine.
I cut ou
14 matches
Mail list logo
