Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!snorkelwacker!mit-eddie!uw-beaver!sumax!polari!6sceng!blm From: blm@6sceng.UUCP (Brian Matthews) Newsgroups: comp.unix.wizards Subject: Re: csh / bsd job control Message-ID: <374@6sceng.UUCP> Date: 24 Mar 90 07:32:41 GMT References: <22821@adm.BRL.MIL> Reply-To: blm@6sceng.UUCP (Brian Matthews) Organization: Six Sigma CASE, Inc. Lines: 15 In article karl_kleinpaste@giza.cis.ohio-state.edu writes: |The SysV csh I built took care of the problem reasonably trivially. |When a job _stopped_, csh would restore the tty state it knew before |the job was started. When the job was restarted, csh would re-assert |the tty state it had when the job last stopped. |When a job _ended_, the tty state was not messed with, on the |assumption that the job knew what it was doing if it changed things. I did something similar, but also had the shell restore the state if the process exited due to a signal, presuming someone killed it and it may not have had a chance to clean up. I suppose it's conceivable that a program could be written that killed itself as a normal exit procedure, but I haven't yet come across a program that badly written :-) -- Brian L. Matthews blm@6sceng.UUCP