Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!husc6!mit-eddie!gatech!akgua!sortac!pls
From: pls@sortac.UUCP (Pat Sullivan)
Newsgroups: comp.unix.wizards
Subject: Re: Big fun with initttab!
Message-ID: <497@sortac.UUCP>
Date: Mon, 1-Jun-87 09:58:22 EDT
Article-I.D.: sortac.497
Posted: Mon Jun  1 09:58:22 1987
Date-Received: Wed, 3-Jun-87 02:40:35 EDT
References: <90@paisana.UUCP>
Reply-To: pls@sortac.UUCP (Pat Sullivan)
Organization: AT&T Tech-NS, Atlanta
Lines: 17

In article <90@paisana.UUCP> demasi@paisana.UUCP writes:
> ...  This process (pure executable) depends
>upon the calling shell to set up its environment and create some
>named pipes.  This process should run at all times while the machine
>(3b2/400, SV.2.0.4) is in multi user mode.  Sounds like a good task
>for an inittab entry, correct?  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.  

At the end of the shell invoked by init, "exec" your pure executable
rather than throwing it in the background.  The pure executable will
then have the same process id as the shell had, and init will be happy
because its child is still running.

============================================================
Pat Sullivan - {akgua|ihnp4}!sortac!pls - voice 404-257-7382