Date: Fri, 24 Feb 1995 09:48:35 -0500 (EST) From: Charlie ROOT <root@vhf.dataradio.com> To: Terry Lambert <terry@cs.weber.edu> Cc: freebsd-questions@FreeBSD.org Subject: Re: Odd behaviour in 2.0R Message-ID: <Pine.NEB.3.91.950224093650.890C-100000@vhf.dataradio.com> In-Reply-To: <9502240050.AA20593@cs.weber.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 23 Feb 1995, Terry Lambert wrote: > > If they are background tasks, they aren't supposed to die when the user > logs out if they were started from a shell other than sh, or if they > were started in sh with "nohup". Terry, thank you for your prompt reply! Ok, but on FreeBSD 1.1.5.1, and on a SVR3.2 box, all processes die off when the user logs out, including the background ones, unless specifically run with nohup. For example, last night, my X server stopped (I sent a HUP signal to it), but all the programs that were running kept running on unconnected virtual terminals! I am a little bit mystified at the bevahiour of 2.0R, as I can't see it being fit for an internet gateway, especially if users can login and leave programs running simply by running them in the background! The obvious question is: how can I - Make the processes part of the shell's process group so that they properly die when lines are hungup? - Patch the kernel so that all processes associated with a terminal get a HUP signal unless they are -HUPCL? The reason behind this need for the HUP signal is that I've written a user timelimit daemon that is executed for each user as they login, and keeps track of how much online time they use, etc..., and I need it to reliably get a HUP signal when the user logs out so that it can shut itself down. **> This program worked under FreeBSD 1.1.5.1 and SVR3.2! Mystified and confused! -- Andrew Webster Network Manager
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.91.950224093650.890C-100000>