Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!seismo!vrdxhq!grebyn!paisana!demasi
From: demasi@paisana.UUCP
Newsgroups: comp.unix.wizards
Subject: Big fun with initttab!
Message-ID: <90@paisana.UUCP>
Date: Wed, 27-May-87 16:51:56 EDT
Article-I.D.: paisana.90
Posted: Wed May 27 16:51:56 1987
Date-Received: Fri, 29-May-87 01:47:21 EDT
Organization: AT&T, Oakton, VA
Lines: 30
Keywords: processes, dying children etc...


Hello Wizards, (male & female, alike)

Here's an interesting problem (I think)  I have a process which
gets kicked off by a shell.  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.  Therefore, making an inittab
entry for the invoking shell is useless.  (Actually, it's a disaster,
since the shell simply:  1)  Sets up the background environment
2)  Invokes the pure executable   3)  Dies  4)  Gets called again
infinitely until init turns it off)

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?  I already have an entry to restart the process
once every time the machine enters multi-user, but I'm hoping for
something to keep it moving.

Waiting to hear from the net,

-- 
Michael C. De Masi - AT&T Communications (For whom I work and not speak)
3702 Pender Drive, Fairfax, Virginia 22030   Phone: 703-246-9555
UUCP:   seismo!decuac!grebyn!paisana!demasi
     "No matter where you go, there you are" - Buckaroo Banzai