Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!pyramid!decwrl!sgi!jmb
From: jmb@patton.SGI.COM (Jim Barton)
Newsgroups: comp.sys.sgi
Subject: Re: (none)
Message-ID: <8748@sgi.SGI.COM>
Date: Tue, 8-Dec-87 11:57:02 EST
Article-I.D.: sgi.8748
Posted: Tue Dec  8 11:57:02 1987
Date-Received: Sun, 13-Dec-87 07:15:47 EST
References:  <8712072239.aa16802@SMOKE.BRL.ARPA>
Sender: daemon@sgi.SGI.COM
Organization: Silicon Graphics Inc, Mountain View, CA
Lines: 26
Summary: No wait3 in System V land

In article <8712072239.aa16802@SMOKE.BRL.ARPA>, STAFF.SAS%CHIP.UChicago@FORSYTHE.STANFORD.EDU (Stuart Schmukler) writes:
> Thank-you Tim.
> 
> I now have a problem that seems to really exist.  Namely the fact that
> the BSD function 'wait3' does not exist in the sgi 'libbsd' or anywhere
> else I can find.
> 
> If 'wait3' really does not exist it _MAYBE_ possible to bypass it, but
> it will take alot of work.  Does anyone have a solution?
> 
> SaS
> -------

The wait3() system call is oriented (and was created specifically for) the
support for job control.  Unfortunately, System V and job control don't mix
very well at all.  This results from the serious implementation differences
between BSD and System V TTY handling, as well as the user visible semantics
(handling of process groups is a good example).

There's no wait3() in IRIS-land, and it's unlikely to appear.  When we
implement a job-control like facility, it WON'T look like Berkeley job
control, but it'll be general purpose (read NOT wired directly into the
TTY driver) and actually usable for controlling programs ... (this isn't
to say we won't supply a compatability interface, but it doesn't say we
will, either).

-- jmb