home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.internals
- Path: sparky!uunet!ftpbox!mothost!white!sapphire.rtsg.mot.com!galena15!murphyn
- From: murphyn@rtsg.mot.com (Neal P. Murphy)
- Subject: Re: Background processes and stdin
- Message-ID: <murphyn.711757239@galena15>
- Sender: news@rtsg.mot.com
- Nntp-Posting-Host: galena15
- Organization: Motorola Inc., Cellular Infrastructure Group
- References: <1992Jul21.023713.2702@hubcap.clemson.edu>
- Distribution: na
- Date: Tue, 21 Jul 1992 22:20:39 GMT
- Lines: 15
-
- rsaripa@saturn.cs.clemson.edu (Saripalli Ramakrishna) writes:
-
- > When a background process needs terminal input,it is stopped.
- > The message "Stopped " appears on the output.
- >...
- > Now if the shell and the process both happen to need input from
- > "stdin",why does not the background process steal whatever I type
- > on the terminal and let the shell wait for input?.
-
- Under sh (Bourne), this is precisely what happens. Under ksh and csh
- and perhaps tcsh, backgroud processes that desire input are stopped,
- because these shells have job control built in. Older SysV flavors
- have shl - shell layers - effectively doing the same thing.
-
- NPN
-