Date: Sun, 15 Jul 2001 19:54:28 +0200 From: Alson van der Meulen <freebsd@alson.linuxfreak.nl> To: freebsd-isp@freebsd.org Subject: Re: Background processes limiting Message-ID: <20010715195428.C10123@md2.mediadesign.nl> In-Reply-To: <Pine.BSF.4.10.10107150907380.46742-100000@bsdie.rwsystems.net> References: <Pine.BSF.4.10.10107150907380.46742-100000@bsdie.rwsystems.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jul 15, 2001 at 09:16:14AM -0500, James Wyatt wrote: > On Sun, 15 Jul 2001, Kal Torak wrote: > > James Wyatt wrote: > > > I have seen such things done in .logout scripts, but usually users can > > > remove the .logout file to prevent the action. One approach might be to > > > have a script run from cron that finds processes with a PPID of "1" > > > (parent now init) and owned by a regular login user and kills them. > > > Another might be to look for regular-user process without an associated > > > tty device. Hope this helps... - Jy@ > > > > Why not just make .logout owned by root? Only give the users group read > > access... That should work, just have a killall -m . -9 or something > > like that in there... > > > > Then just have your cron job running every so often to clean up anything > > that might of somehow slipped though the cracks... > > If the file is owned by root, but in a directory owned by joe.user, then > Joe can easily 'rm' the file himself. I liked the idea of using a .logout, man chflags... look at schg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010715195428.C10123>