From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from pantransit.smar.reptiles.org ([198.96.117.26]) by hawkwind.utcs.utoronto.ca with SMTP id <24728>; Thu, 5 Feb 1998 16:59:28 -0500
Received: (qmail 22054 invoked by uid 204); 5 Feb 1998 19:59:04 -0000
Date:	Thu, 5 Feb 1998 14:59:03 -0500
Message-ID: <19980205195903.22053.qmail@pantransit.smar.reptiles.org>
From:	smarry@pantransit.smar.reptiles.org
To:	culliton@clark.net, smarry@pantransit.smar.reptiles.org
Subject: Re: "rc" shell maintainer?
Cc:	broman@nosc.mil, debian-devel@lists.debian.org,
	rc@hawkwind.utcs.toronto.edu

Tom Culliton <culliton@clark.net> writes:
>On 05 Feb 1998 05:01:30 GMT, smarry@pantransit.smar.reptiles.org wrote:
>[...]
>> and the PID that wait(2) returned is lost.  rc loops forever calling
>> wait(2) with no children, waiting for the lost PID to turn up.
>
>Shouldn't the "interrupt_happened" flag prevent this?

Unfortunately, no.  Whether it's set to TRUE or FALSE, the setjmp
block gets rerun, and the PID returned from wait(2) (or really wait4(2),
I guess) is discarded.

I should clarify that I'm not the one having the problems with glibc.
They are indeed using RedHat, not sure what version. I'm using
libc.so.5.3.12, which turns out to be out of date, but it's the same
version as on the RedHat distribution of the other system in question.