Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!ames!cit-vax!oberon!sdcrdcf!psivax!csun!aeusemrs
From: aeusemrs@csun.UUCP
Newsgroups: comp.unix.wizards
Subject: Re: Big fun with initttab!
Message-ID: <626@csun.UUCP>
Date: Mon, 1-Jun-87 18:21:16 EDT
Article-I.D.: csun.626
Posted: Mon Jun  1 18:21:16 1987
Date-Received: Fri, 5-Jun-87 03:27:03 EDT
References: <90@paisana.UUCP>
Reply-To: aeusemrs@csun.UUCP (Mike Stump)
Organization: California State University, Northridge
Lines: 26

In article <90@paisana.UUCP> demasi@paisana.UUCP (Michael C. De Masi) writes:
+---------
|Hello Wizards, (male & female, alike)
|...  This process (pure executable) depends
|upon the calling shell to set up its environment and create some
|named pipes.  ...  The only problem is that the process
|that must be kept continuously running is a background process, which
|gets called by the afformentioned shell, which croaks immediately
|after invoking the background process. ...
|Does anybody know of a way that I can get init to watch for the death
|of the Child process here and then have it call the invoking shell to
|restart said process?
|
|Michael C. De Masi - AT&T Communications (For whom I work and not speak)
+---------

Michael,  How `bout:

    1)  Having the shell script wait for the child itself, via wait.
    2)  Having the shell script execute it in the forground.
    3)  Have the shell program exec to the other program.
    4)  Make two programs, one that behaves the old way, and one that
        behaves as described above for use with inittab.
-- 
Mike Stump, Cal State Univ, Northridge Comp Sci Department
uucp: {sdcrdcf, ihnp4, hplabs, ttidca, psivax, csustan}!csun!aeusemrs