Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Message-Id:	<3.0.5.32.20030323102855.007fa310@incoming.verizon.net>
X-Sender:	vze1u1tg AT incoming DOT verizon DOT net
Date:	Sun, 23 Mar 2003 10:28:55 -0500
To:	"Elfyn McBratney" <elfyn AT exposure DOT org DOT uk>, <cygwin AT cygwin DOT com>
From:	"Pierre A. Humblet" <Pierre DOT Humblet AT ieee DOT org>
Subject:	Re: Hate to say it, but...I've got the (dreadded) PID problem
In-Reply-To:	<006101c2f0e6$58185850$086a86d9@ellixia>
Mime-Version:	1.0

At 02:46 AM 3/23/2003 -0000, Elfyn McBratney wrote:
>Hate to say it, but...I've got the (dreadded) PID problem

Do you mean e.g.
http://cygwin.com/ml/cygwin/2003-03/msg01350.html

>Hello everyone,
>
>I haven't been here in a while as my main computer died and I was
>practically Cygwin'less. I have just finished a fresh install of Windows
>2000 Pro/SP3 with all of the latest cygwin bits (that I need) which is
>running 1.3.22 . I'll get to the point...While fixing the permissions on my

You shouldn't *have to* do that if you use the latest setup.
Next time it happens that you have to, could you capture (getfacl ) an 
offending file, the directory it is in and the top directory (c:\ ?) under 
which setup created the hierarchy. Note that if your fresh install is over
existing directories, unexpected interactions can take place.

>installation (via a combination of `find -exec' and `chmod'), and when I say
>while I mean pretty much straight away, I started getting tones of "Access
>is denied" messages from find. Sure enough I couldn't do anything from my
>shell. I hate to say it but I can't do much with cygwin now (need to build a
>lot of tools) as after running a few fork()ing processes I get an "Access is
>denied" message from the binary that's being executed.
>
>I've attached the output of `cygcheck -svr' and the strace output. I don't
>want to sound like I'm bitching about this, really I'm not :-) If there's
>anything I can do to provide info please ask.
>
The strace shows:
 147 22879819 [main] bash 1364 read_sd: file = G:\Cygwin\bin\which.exe:
len=152
  119 22879938 [main] bash 1364 check_file_access: flags 1, ret 0

This says that which.exe is executable. No permission issue.

   72 22880544 [main] bash 1364 fork: entering
  129 22880673 [main] bash 1364 stack_base: bottom 0x230000, top 0x30000,
stack 0x22F520, size 2784, reserve 2097152
   78 22880751 [main] bash 1364 fork_parent: CreateProcess
(G:\Cygwin\bin\bash.exe, G:\Cygwin\bin\bash.exe, 0, 0, 1, 20, 0, 0,
0x22F9B0, 0x22FA00)
  476 22881227 [main] bash 1364 seterrno_from_win_error:
/netrel/src/cygwin-1.3.22-1/winsup/cygwin/fork.cc:482 windows error 5
  112 22881339 [main] bash 1364 geterrno_from_win_error: windows error 5 ==
errno 13
   72 22881411 [main] bash 1364 fork_parent: CreateProcessA failed, Win32
error 5

But bash cannot fork itself. No idea why.

Pierre


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -