Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!emory!gatech!bloom-beacon!eru!hagbard!sunic!mcsun!hp4nl!phigate!prle!prles2!prl.philips.nl!hooft
From: hooft@prl.philips.nl (Peter van Hooft)
Newsgroups: comp.sys.apollo
Subject: Re: Keeping DM from killing process at logout
Message-ID: <2729@prles2.prl.philips.nl>
Date: 17 Apr 91 19:21:05 GMT
References: <1991Apr15.221826.11448@cci632.cci.com> <rtb.671799710@cernapo.cern.ch> <1129@eba.eb.ele.tue.nl>
Sender: news@prles2.prl.philips.nl
Lines: 23

In <1129@eba.eb.ele.tue.nl> wjw@ebh.eb.ele.tue.nl (Willem Jan Withagen) writes:

>In article <rtb.671799710@cernapo.cern.ch> 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

And the daemons are killed when you log out.

>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.

Willem Jan suggests to start the daemon from a rsh

>	Willem Jan Withagen.

With sr10.*, you can of course start daemons with 
/etc/server -p your_evil_daemon &


Peter van Hooft    Philips Research Labs, Eindhoven, the Netherlands
Email: hooft@prl.philips.nl SERI: HOOFT:NLWAYA01 Voice: +31 40744327 
X400:  /PN=PJG.VanHooft/O=research/PRMD=philips400/ADMD=400net/C=nl/