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: Bug or feature?
- Message-ID: <9208271420.AA01970.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: Thu, 27 Aug 1992 06:20:19 GMT
- Approved: bug-bash@prep.ai.mit.edu
- Lines: 22
-
- > If you do
- >
- > for i in 0 1 2 3 4 5 6 7 8 9; do sleep 100; done
- >
- > and then hit ^Z, only the sleep gets backgrounded, not the for loop.
- > Repeat the ^Z's and you end up with 10 seperate background processes.
- > This is presumably because the for loop is not a seperate process,
- > still, after a user on my system managed to create 13 simultaneous big
- > processes this way, I am wondering if other shells with job control
- > work the same way.
-
- The BSD sh (ash) and zsh both work the same way. ksh makes the entire
- loop unstoppable.
-
- Chet
-
- --
- ``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
-
-