rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: smarry@pantransit.smar.reptiles.org
To: culliton@clark.net, smarry@pantransit.smar.reptiles.org
Cc: broman@nosc.mil, debian-devel@lists.debian.org,
	rc@hawkwind.utcs.toronto.edu
Subject: Re: "rc" shell maintainer?
Date: Thu, 5 Feb 1998 14:59:03 -0500	[thread overview]
Message-ID: <19980205195903.22053.qmail@pantransit.smar.reptiles.org> (raw)

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.


             reply	other threads:[~1998-02-05 21:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-02-05 19:59 smarry [this message]
  -- strict thread matches above, loose matches on Subject: below --
1998-02-05  5:01 smarry
1998-02-05 15:25 ` Tom Culliton
1998-02-06 17:45 ` Tim Goodwin
1998-02-04 21:23 Vincent Broman
1998-02-05  1:17 ` Tom Culliton
1998-02-05 11:46 ` Tim Goodwin
1998-02-05 21:48   ` Vincent Broman
1998-02-06 18:00     ` Tim Goodwin
1998-02-06 22:54       ` Vincent Broman
1998-02-09 20:31       ` Vincent Broman
1998-02-09 23:45       ` Vincent Broman
1998-02-10 23:26         ` Tom Culliton
1998-02-11 10:45           ` Tim Goodwin
1998-02-11 22:23             ` Tom Culliton
1998-02-12 10:23               ` Tim Goodwin
1998-02-11 21:55           ` Vincent Broman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=19980205195903.22053.qmail@pantransit.smar.reptiles.org \
    --to=smarry@pantransit.smar.reptiles.org \
    --cc=broman@nosc.mil \
    --cc=culliton@clark.net \
    --cc=debian-devel@lists.debian.org \
    --cc=rc@hawkwind.utcs.toronto.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).