Xref: utzoo comp.sys.sgi:5071 comp.unix.wizards:23124 Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uwm.edu!zaphod.mps.ohio-state.edu!usc!snorkelwacker!bloom-beacon!pit-manager.MIT.EDU!jik From: jik@pit-manager.MIT.EDU (Jonathan I. Kamens) Newsgroups: comp.sys.sgi,comp.unix.wizards Subject: Re: SIGSTOP and SIGCONT rules Keywords: signal, process groups Message-ID: <1990Jul27.183343.22225@athena.mit.edu> Date: 27 Jul 90 18:33:43 GMT References: Sender: daemon@athena.mit.edu (Mr Background) Reply-To: jik@pit-manager.MIT.EDU (Jonathan I. Kamens) Distribution: usa Organization: Massachusetts Institute of Technology Lines: 31 In article , srp@babar.mmwb.ucsf.edu (Scott R. Presnell) writes: |> If I background the process and logout of the csh that started the |> process, then the first time I send it STOP from another csh, the process |> exits. This is not my experience on my BSD 4.3 system, which implies that either your version of Unix does something funky with STOP AND CONT that 4.3 doesn't, or that the process to which you're sending the STOP signal does something funky that causes it to exit if it doesn't have a tty when it gets STOPped. I tested this by logging into my machine via telnet, typing "sleep 3000 &", logging out, and then STOPping and CONTing the process from another xterm window as the same user. |> What are the rules for sending SIGSTOP and SIGCONT to a process? |> From csh? From a daemon that nolonger has a controlling tty? (I'm more |> interested in the daemon rules.) How does the process group relate to this? As far as I know (and I hope people will correct me if I'm wrong, because I would like to hear about it), there aren't really any "rules" for sending STOP and CONT to another process. They are treated like any other signals. If this isn't true under IRIX and/or SysV, I'd sure like to hear about it. Jonathan Kamens USnail: MIT Project Athena 11 Ashford Terrace jik@Athena.MIT.EDU Allston, MA 02134 Office: 617-253-8495 Home: 617-782-0710