background process persist-or-die when its parent shell dies

background process persist-or-die when its parent shell dies

Post by John R. Prie » Fri, 19 Nov 1993 23:29:09

I would like to know what causes a child to persist or not-persist when
the originating shell terminates.  My environment is SUN openwindows.

For example, some background child processes (a & for
example) persists after I exit or kill the shell where I invoked it;
But other background processes of an apparently similar type will
immediately terminate when their parent shell exits.

Why?  Or in other words, how can I write my invokation so that I have
control over whether the child background process is "dependent" on the
parent or not?

My work-around is to invoke my via  at -qb
in order to ensure that it will persist after the "parent" invoking it dies.
But this seems round-about.


John PRieur


1. Solaris 9 - nohup'd background child process dying when ^C pressed in parent (/sbin/sh)

Anyone know why when using /sbin/sh as the shell, you nohup background
a process, and then hit ^C at the command line why the background
child process dies ?

If I exec /bin/ksh, this doesn't occur.
......... ..- -. .. -..- .-. ..- .-.. . ... ............
.-- .. -. -... .-.. --- .-- ... -.. .-. --- --- .-.. ...

Sean O'Neill

2. Mail and vi

3. Is there a fix for problem w vi sessions not dying when parent dies?

4. Apache 1.2: messing about with authentification.

5. Is there a fix for sessions not dying when parent dies?

6. Help!! Kernel Won't Compile!

7. child processes not dying with parent process??


9. PC-NFS, printing, bannerpage. die.die.die

10. Zombie die die die

11. /ethan die,die,die

12. Help: Keeping several processes in sync - one dies they all die

13. Son processes don't die when father die..