Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site hou3c.UUCP Path: utzoo!watmath!clyde!burl!hou3c!ka From: ka@hou3c.UUCP (Kenneth Almquist) Newsgroups: net.unix Subject: Questions about Berkeley job control Message-ID: <887@hou3c.UUCP> Date: Fri, 19-Oct-84 14:23:22 EDT Article-I.D.: hou3c.887 Posted: Fri Oct 19 14:23:22 1984 Date-Received: Sun, 21-Oct-84 14:16:14 EDT Distribution: net Organization: Bell Labs, Holmdel, NJ Lines: 11 First, I have a program that forks off a child and then exits. This allows the user to do something else while the program finishes. I call signal to cause the program to ignore SIGTSTP so that the user won't accidentally stop it. Is this the right approach? Do I have to call sigset instead of signal if I want my program to work under 4.1 BSD? I have another program that catches hangup signals. However, if the user stops the program and then hangs up the terminal, my program appears to go away without executing the hangup signal processing routine. Is it possible for a stopped job to trap hangup signals? Kenneth Almquist