From owner-freebsd-current Sun Apr 5 08:19:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA29755 for freebsd-current-outgoing; Sun, 5 Apr 1998 08:19:16 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rs3.rrz.Uni-Koeln.DE (5508@rs3.rrz.Uni-Koeln.DE [134.95.100.214]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA29750 for ; Sun, 5 Apr 1998 08:19:13 -0700 (PDT) (envelope-from H.Husic@Uni-Koeln.DE) Received: from localhost (aaz09@localhost) by rs3.rrz.Uni-Koeln.DE (8.8.5/8.8.4) with SMTP id RAA48455 for ; Sun, 5 Apr 1998 17:19:10 +0200 Date: Sun, 5 Apr 1998 17:19:10 +0200 (MST) From: Hrvoje husic To: freebsd-current@FreeBSD.ORG Subject: lastlogs 'invalid hostname' Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a decent problem with a 3.0-CURRENT machine here. [hhusic@dvpraktikum hhusic]$ w 5:13PM up 6:25, 9 users, load averages: 1.01, 1.03, 0.98 USER TTY FROM LOGIN@ IDLE WHAT [...] rstevens p8 invalid hostname 5:11PM 1 -bash (bash) [...] [hhusic@dvpraktikum hhusic]$ The same entry goes into the lastlig, so the users originating host is hidden in the logfiles. "netstat" and "netstat -n" does not have problems resolving the hostname, but as there are quite a lot of connections I can't really tell, which one is THE one. (but I'd guess it might be pool3-82.netcologne.de [195.14.235.82]) -- Hrvoje Husic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message