Date: Mon, 4 Nov 2002 21:05:15 +0000 From: Jez Hancock <jez.hancock@munk.nu> To: FreeBSD questions List <freebsd-questions@FreeBSD.ORG> Subject: Re: user dead but appears still logged in in 'w' output Message-ID: <20021104210515.GA3165@users.munk.nu> In-Reply-To: <20021104191630.GA28469@ei.bzerk.org> References: <20021104113116.GA1080@users.munk.nu> <200211040734.49151.ph1@cogeco.ca> <20021104180006.GA2434@users.munk.nu> <20021104191630.GA28469@ei.bzerk.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Nov 04, 2002 at 08:16:30PM +0100, Ruben de Groot wrote: > On Mon, Nov 04, 2002 at 06:00:06PM +0000, Jez Hancock typed: > > On Mon, Nov 04, 2002 at 07:34:49AM -0500, david wrote: > > > On Monday 04 November 2002 06:31, Jez Hancock wrote: > > > > I have a problem with a user who was idle for a long period > > > > of time which I killed off by terminating the associated > > > > login process for that user's ssh connection. > > > > > > Try would also have a shell session going, kill that as well. > > Well, what I actually did was find out the login shell session pid > > belonging to the user in question and 'kill -9' that proc - after > > this the rest of the processes spawned by > > the login did all die as well. Unfortunately the user still appeared > > to be logged in in 'w' output. Whether you can class it as a 'bug' or > > not I don't know, since killing a user's login shell isn't the de facto > > method of forcefully logging a user out (or is it!?;) > > Don't use 'kill -9'. That signal is meant for desperate people. Use plain > kill (-15) and a wellbehaving process will neatly close all administration, > including wtmp. Cheers, that's probably what caused the problem ;) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021104210515.GA3165>