Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!think.com!mintaka!bloom-beacon!eru!hagbard!sunic!mcsun!hp4nl!svin02!eba!ebh!wjw From: wjw@ebh.eb.ele.tue.nl (Willem Jan Withagen) Newsgroups: comp.sys.apollo Subject: Re: Keeping DM from killing process at logout Message-ID: <1129@eba.eb.ele.tue.nl> Date: 17 Apr 91 07:57:55 GMT References: <1991Apr15.221826.11448@cci632.cci.com> Sender: news@eb.ele.tue.nl (The News system) Organization: Eindhoven University of Technology, The Netherlands Lines: 30 In article rtb@cernapo.cern.ch (Rainer Tobbicke) writes: =>mth@cci632.cci.com (Michael Hickman) writes: => => =>>I have written a program in PERL that forks daemon process. I have the =>>daemon process do a ioctl(TTY, &TIOCNOTTY, 0), and even give it a unique =>>process group id with setpgid(0, $$). When running under an rlogin shell, =>>I can logout and the daemon process keeps running. However, if I'm using =>>the Display Manager, it does it's utmost to kill the process when I logout. As far as I was able to drag this for my Apollo-support person long time ago. It seems that when the DM logs a user off, it sends all the processes owned by the display/user not only the signal SIGHUP but also SIGAPOLLO. Now the later is not caught by most of the programs (like shells, etc :) ) and hence the burst into tears, and then kill themselves. Once in a while it helps to do a crp to the same node. It is always effective to do a rsh on the same node and fork the froces from there. Then it owned by a ttyp and doesn't get stabbed in the back by a SIGAPOLLO. Please correct me if I tell it wrong, Willem Jan Withagen. PS: If this is true, then it might be a good one for the questions list kept by Jim Rees. You can get it at dabo.citi.umitch.edu Eindhoven University of Technology DomainName: wjw@eb.ele.tue.nl Digital Systems Group, Room EH 10.10 P.O. 513 Tel: +31-40-473401 5600 MB Eindhoven The Netherlands