Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!AUREL.CALTECH.EDU!bfox
From: bfox@AUREL.CALTECH.EDU (Brian Fox)
Newsgroups: gnu.bash.bug
Subject: Bash 1.01 Job Control handling buglet
Message-ID: <8907051941.AA13442@aurel.caltech.edu>
Date: 5 Jul 89 19:41:21 GMT
References: <8907051526.AA07699@orion>
Sender: daemon@tut.cis.ohio-state.edu
Reply-To: bfox@aurel.caltech.edu.date.wed,
        5.Jul.89.11.26.12.EDT.From.bet@orion.mc.duke.edu         
     (Bennett Todd)
Distribution: gnu
Organization: GNUs Not Usenet
Lines: 16


   It appears that bash isn't ignoring TSTP. Since in general there
   isn't any parent to continue, it is a fairly severe hang when bash goes
   to sleep (requires sending it a CONT from another shell).

   -Bennett
   bet@orion.mc.duke.edu
   P.S. Mail is really flaky around here -- could you please (attempt to)
   ACK this note? Thanks!

Please be specific, and explain where you have had a problem with this?
In a login shell, Bash ignore stop signals.  In a non-login interactive
shell, Bash does not ignore stop signals.  I haven't had a problem with
this.

Brian