Mail Archives: cygwin-apps/2000/07/06/20:12:56
Indeed they are,
I'm told that it's standard/common practice to do the close() loop
before spawning the main daemon though.
0 is Std_in, 1 is std_out and 2 is std_err.
So squid on cygwin is stackdumping when close(2) is called. I have
worked around this in squid now, so it's certainly not urgent (for me),
but the behaviour is different than on most un*xes.
From: Charles Wilson [mailto:cwilson AT ece DOT gatech DOT edu]
Sent: Friday, 7 July 2000 10:08 AM
To: Robert Collins
Cc: cygwin-apps AT sourceware DOT cygnus DOT com
Subject: Re: stackdump revisited
Call me crazy, but aren't fd's 0,1 and 2 == stdin, stdout, stderr (in
> Robert Collins wrote:
> Thanks all for your patience with my stackdumping squid!
> this time I have made real progress...
> squid goes thru the following loop when before it starts up the very
> first worker instance.
> for (i = 0; i < Squid_MaxFD; i++)
> when i=2 it stackdumps. Are fd's 0, 1 and 2 reserved? I am looking
> into whether squid _needs_ to close these, or if it's an old hack
> still present..
> Thanks in advance,
- Raw text -