From owner-freebsd-bugs@FreeBSD.ORG Sat Dec 8 13:30:02 2007 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D7BE116A417 for ; Sat, 8 Dec 2007 13:30:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id C6E7F13C458 for ; Sat, 8 Dec 2007 13:30:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id lB8DU2bp089529 for ; Sat, 8 Dec 2007 13:30:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id lB8DU2dQ089524; Sat, 8 Dec 2007 13:30:02 GMT (envelope-from gnats) Date: Sat, 8 Dec 2007 13:30:02 GMT Message-Id: <200712081330.lB8DU2dQ089524@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Pete French Cc: Subject: Re: bin/117773: 'w -n' still dispalys names for IPv6 connections X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Pete French List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Dec 2007 13:30:02 -0000 The following reply was made to PR bin/117773; it has been noted by GNATS. From: Pete French To: bob@norcalttora.com, bug-followup@FreeBSD.org Cc: Subject: Re: bin/117773: 'w -n' still dispalys names for IPv6 connections Date: Sat, 08 Dec 2007 13:29:48 +0000 > I tried reproducing this bug hoping to be able to fix it but had > a little bit of trouble reproducing it. From what I can see on > RELENG_7 and RELENG_6 the -n flag will work the same way for IPv4 > and IPv6. In the case that -n is set w(1) just reads from /var/run/utmp > and basically dumps the address that's written there. Sorry for not getting back to you before now! Had lost this email in a pile of about 400 others. Thanks for starting to look at the issue for me. I suspect you are right, and that something is back resolving the hostnames before writing them into the utmp file. 'last' has the same erreft - downs the hostnames if the resolve. > I'm wondering if you can share part of your utmp file to verify > that the hostname is being written in to that file rather than the > IPv6 address? Sure - heres todays from a 6.2-STABLE machine with the same problem http://toybox.twisted.org.uk/~pete/utmp.gz The login from dilbert.ticketswitch.com should be comming from 2002:57e0:1d4e:1:20e:cff:fedc:c380 cheers, -pete.