home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: gnu.bash.bug
- Path: sparky!uunet!cis.ohio-state.edu!odin.ins.cwru.edu!chet
- From: chet@odin.ins.cwru.edu (Chet Ramey)
- Subject: Re: "tee | bash -i" doesn't work?
- Message-ID: <9209111829.AA18237.SM@odin.INS.CWRU.Edu>
- Sender: gnulists@ai.mit.edu
- Reply-To: chet@po.cwru.edu
- Organization: GNUs Not Usenet
- References: chet@odin.ins.cwru.edu (Chet Ramey)
- Distribution: gnu
- Date: Fri, 11 Sep 1992 10:29:46 GMT
- Approved: bug-bash@prep.ai.mit.edu
- Lines: 30
-
- > I can't seem to get out of:
- >
- > $ tee | bash -i
- >
- > This is true of ash and ksh as well.
-
- This is a job control issue. When an interactive bash starts up in a
- job control environment, it puts itself into a new process group and
- makes itself the process group leader. When bash is started as above,
- it is not a process group leader, and when it makes itself one, leaves
- the two halves of the pipeline in different process groups, fighting
- over the terminal, which is disastrous. The `tee' gets hit with SIGTSTP
- and stops.
-
- `tee logf | bash -s' works because the bash started is non-interactive.
- sh works because it doesn't know anything about job control.
-
- --
- ``The use of history as therapy means the corruption of history as history.''
- -- Arthur Schlesinger
-
- Chet Ramey, Case Western Reserve University Internet: chet@po.CWRU.Edu
-
-
- --
- ``The use of history as therapy means the corruption of history as history.''
- -- Arthur Schlesinger
-
- Chet Ramey, Case Western Reserve University Internet: chet@po.CWRU.Edu
-
-