home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!kithrup!stanford.edu!ames!haven.umd.edu!darwin.sura.net!gatech!bloom-beacon!eru.mt.luth.se!lunic!sunic!news.funet.fi!hydra!klaava!klaava!hurtta
- From: hurtta@cs.Helsinki.FI (Kari E. Hurtta)
- Newsgroups: comp.os.linux
- Subject: Re: Background processes not dying on parent exit
- Message-ID: <HURTTA.92Sep6170232@plootu.Helsinki.FI>
- Date: 6 Sep 92 15:02:32 GMT
- References: <1992Aug31.040048.27053@athena.mit.edu>
- <1992Aug31.071515.24296@klaava.Helsinki.FI> <20189@plains.NoDak.edu>
- Sender: news@klaava.Helsinki.FI (Uutis Ankka)
- Organization: Department of Computer Science, University of Helsinki, Finland
- Lines: 26
- In-Reply-To: person@plains.NoDak.edu's message of 6 Sep 92 11: 21:06 GMT
-
- <This is said here one time earlier at least, but seems that someones don't
- understand without repeating.>
-
- In article <20189@plains.NoDak.edu> person@plains.NoDak.edu (Brett G Person ) wrote:
- > Why is it done this way? This is kinda sloppy. I know that
- > somethimes unix will forget to kill one of my processes, but it
- > doesn't seem to happen very often. Why would linux be designed this
- > way?
- >
- > I think that all processes that aren't specifically nohup'ed should
- > have to die when their parents die.
-
- Linux does what programs ask to it do.
-
- It is shell, what is designed this way. From csh's manual page:
- "All processes detached with & are effectively nohup'd." This
- apply also to tcsh.
-
- So ask from writer of csh.
-
- - K E H
- ( Kari.Hurtta@Helsinki.FI,
- hurtta@cc.Helsinki.FI,
- hurtta@cs.Helsinki.FI,
- HURTTA@FINUH.BITNET
- )
-