From owner-freebsd-questions Mon Apr 13 20:36:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA06326 for freebsd-questions-outgoing; Mon, 13 Apr 1998 20:36:11 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from federation.addy.com (federation.addy.com [207.239.68.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA06305 for ; Tue, 14 Apr 1998 03:36:03 GMT (envelope-from fbsdlist@federation.addy.com) Received: from localhost (fbsdlist@localhost) by federation.addy.com (8.8.5/8.6.12) with SMTP id XAA26629; Mon, 13 Apr 1998 23:35:42 -0400 (EDT) Date: Mon, 13 Apr 1998 23:35:41 -0400 (EDT) From: Cliff Addy To: Dima Dorfman cc: freebsd-questions@FreeBSD.ORG Subject: Re: Forced logoff In-Reply-To: <3.0.5.32.19980413134702.00962cc0@207.213.224.25> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 13 Apr 1998, Dima Dorfman wrote: > That's not really what I'm looking for. Let's say, there is a user that is > about to break into your system. You _could_ use 'shutdown -k', but let's > say that your boss is writing a very important document, and he's not > autosaving it. You log everyone off, and your boss kills you because he > needs to write it all over again. Oh, well then just use "ps aux | grep userid" for whatever user you're interested in and kill the pid of his shell. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message