home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.internals
- Path: sparky!uunet!cs.utexas.edu!usc!sdd.hp.com!caen!hellgate.utah.edu!fcom.cc.utah.edu!cs.weber.edu!terry
- From: terry@cs.weber.edu (A Wizard of Earth C)
- Subject: Re: How can a Unix process put itself in background?
- Message-ID: <1992Sep12.020457.5127@fcom.cc.utah.edu>
- Sender: news@fcom.cc.utah.edu
- Organization: Weber State University (Ogden, UT)
- References: <1992Sep11.170405.28836@tandem.com> <18qopsINN12n@early-bird.think.com> <1992Sep11.222546.3878@tandem.com>
- Date: Sat, 12 Sep 92 02:04:57 GMT
- Lines: 29
-
- In article <1992Sep11.222546.3878@tandem.com> norcott_bill@tandem.com (Bill Norcott) writes:
- >Sure, all UNIX user processes are created by fork(). So the process
- >that wants to put itself into the background was created by fork().
- >And it's parent should be using waidpid() or wait() to wait for the
- >death of the child. But the original question was, how can the guy's
- >existing (child) process put ITSELF in the background. This is where
- >setsid() and setpgid() are used.
-
- Say! That's right! He never said he actually wanted the shell that
- launched the program to return -- he just wanted the child in the background
- instead of the foreground! 8-). 8-).
-
- Seriously, I think he wanted the parent (the shell) to keep running
- as if the process had completed, but leaving the process in the background.
- This is what everything he has posted so far has implied, although not as
- tersely.
-
-
- Terry Lambert
- terry_lambert@gateway.novell.com
- terry@icarus.weber.edu
- ---
- Any opinions in this posting are my own and not those of my present
- or previous employers.
- --
- -------------------------------------------------------------------------------
- "I have an 8 user poetic license" - me
- Get the 386bsd FAQ from agate.berkeley.edu:/pub/386BSD/386bsd-0.1/unofficial
- -------------------------------------------------------------------------------
-