Stopped (tty output)

Jonathan I. Kamens jik at athena.mit.edu
Mon Mar 4 11:37:18 AEST 1991


In article <1991Mar2.215641.10509 at DMI.USherb.CA>, forget at pluton (Yves Forget) writes:
|> Could someone please explain me why jobs I execute in background stop
|> with the message you see on the subject line ?

  From the man page tty(4):

     When using the new terminal driver with the LTOSTOP bit set
     in the local modes, a process is prohibited from writing on
     its control terminal if it is not in the distinguished pro-
     cess group for that terminal.  Processes which are blocking
     or ignoring SIGTTOU signals or which are in the middle of a
     vfork(2) are excepted and allowed to produce output.

  In other words, certain processes don't want their output to go to the
terminal unless they're controlling the terminal.  For example, processes that
use curses don't want to be writing to the terminal if they're running in the
background.  Processes of this sort set the LTOSTOP bit in their terminal
modes, telling the kernel to automatically send them a signal which (by
default) stops them if they try to write to the terminal and they're not
currently controlling it.

-- 
Jonathan Kamens			              USnail:
MIT Project Athena				11 Ashford Terrace
jik at Athena.MIT.EDU				Allston, MA  02134
Office: 617-253-8085			      Home: 617-782-0710



More information about the Comp.unix.shell mailing list