Re: Bug in builtin wait when there are no kids?

[Byron Rakitzis <byron>]

Re: the bug rich found. This had nothing to do with the wait system call
and has since been fixed.

Re: ignoring your mail. I don't think it's fair to say that; I have
tried to pay close attention to every piece of mail I've received, at
least to say "ok, I've read this, I'll digest at it later", but there
is just no way that I can get around to doing everything on everybodies
wish list and still have time to breathe. I trust people can appreciate
this.

Re: broken wait. There are, as you point out, two sides to the
argument.  One the one hand, an interrupt in any routine which
performs allocation could hose rc, and it is true that I made the
tacit assumption that interrupts are just not part of the game.
On the other hand, rc is "broken", as seen by the opposing view.

In my defense, I can only offer the following couple of thoughts: 1) I
never use signal handlers myself, and I would never use them for more
than clean up & exit type work. 2) I do not consider myself knowlegable
enough to deal with the problem right now. I don't know how signal()
is implemented say, in System V, and nor do I feel particularly inclined
to try to find out in order to fix signal handlers in rc. Frankly, there
are more important things for me to do with my life. 3) However, if someone
feels the urge to work on this problem, and has a real handle on it, then
I will do my best to act as a maintainer of rc's source.

I'm sorry if this attitude is disappointing to anyone, but after nearly
a year of work on rc, I feel it is time to shunt it off to one side. Unless
someone can show me a real reason (not the fake example cited above) why
signal handlers in rc need to be fixed, then I'm not going to get particularly
excited about this bug in rc.