From owner-freebsd-questions Fri Jun 19 06:24:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA10808 for freebsd-questions-outgoing; Fri, 19 Jun 1998 06:24:52 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from peanut.readington.com ([207.207.198.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA10795 for ; Fri, 19 Jun 1998 06:24:45 -0700 (PDT) (envelope-from chrismar@peanut.readington.com) Received: from localhost (chrismar@localhost) by peanut.readington.com (8.8.7/8.8.7) with SMTP id IAA18748; Fri, 19 Jun 1998 08:28:41 -0400 (EDT) (envelope-from chrismar@peanut.readington.com) Date: Fri, 19 Jun 1998 08:28:41 -0400 (EDT) From: Chris Martino To: Cliff Addy cc: questions@FreeBSD.ORG Subject: Re: "ghost" user In-Reply-To: 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 We came accross this problem the other day here at work, and we were trying to find a solution w/out rebooting as well. What ended up working was logging in as many times as it took us to use the tty that was "ghosted" again, and then properlly logging out. This worked on BSDI, and I'm assuming it will on FreeBSD too..=) Chris -- Chris Martino chrismar@readington.com On Fri, 19 Jun 1998, Cliff Addy wrote: > I'm seeing something a little wierd on one of our servers. A who shows > > apache ttyp0 Jun 19 08:06 (borg) > gschryer ttyp2 Jun 18 15:08 (135.205.95.104) > > but gschryer is *not* logged in. Furthermore, a w shows > > USER TTY FROM LOGIN@ IDLE WHAT > apache p0 borg 8:06AM - w > gschryer p2 H-135-205-95-104 Thu03PM 16:59 - > > i.e. this "ghost" user appears to be doing nothing. If I do a > "ps aux | grep gschryer" it returns nothing, i.e. no processes owned by > gschryer, not even a shell. And grepping for "p2" also returns nothing, > there aren't even any processes owned by *any* ttys other than the p0 I'm > on. > > Huh? gschryer pointed this out to me, so I don't think there's anything > sinister going on. But how could this happen and how (other than a > reboot) can I make it go away? > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message