From owner-freebsd-isp Sat Jul 14 22: 5:27 2001 Delivered-To: freebsd-isp@freebsd.org Received: from www.golsyd.net.au (golsyd.net.au [203.57.20.1]) by hub.freebsd.org (Postfix) with ESMTP id C95D337B401 for ; Sat, 14 Jul 2001 22:05:24 -0700 (PDT) (envelope-from kaltorak@quake.com.au) Received: from [203.164.12.28] by www.quake.com.au (NTMail 4.30.0012/AB6169.63.5724aadf) with ESMTP id jyacaaaa for ; Sun, 15 Jul 2001 15:04:02 +1000 Message-ID: <3B512528.BD0C9C21@quake.com.au> Date: Sun, 15 Jul 2001 15:07:52 +1000 From: Kal Torak X-Mailer: Mozilla 4.73 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: James Wyatt Cc: =?iso-8859-1?Q?Mat=EEss?= Elsbergs , Marc Veldman , freebsd-isp@freebsd.org Subject: Re: Background processes limiting References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org 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... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message