bin/57089: "w" does not honor the -n option
Kirk Strauser
kirk at strauser.com
Mon Sep 22 16:40:16 PDT 2003
The following reply was made to PR bin/57089; it has been noted by GNATS.
From: Kirk Strauser <kirk at strauser.com>
To: Dima Dorfman <dima at trit.org>
Cc: FreeBSD-gnats-submit at FreeBSD.org, brian at FreeBSD.org
Subject: Re: bin/57089: "w" does not honor the -n option
Date: Mon, 22 Sep 2003 18:39:18 -0500
--=-=-=
Content-Transfer-Encoding: quoted-printable
At 2003-09-22T22:43:00Z, Dima Dorfman <dima at trit.org> writes:
> and it looks like that rationale still applies.
That makes a certain kind of sense, I suppose.
> I've cc'd brian (who made that change) to see whether he has any input on
> this. The issue is: So, you want to see numeric addresses--but for which
> family? If a host resolves to a v4 and v6 address, which one should be
> displayed?
Ideally, you'd see the address of the socket that the user is connecting on.
For diagnostic purposes, it'd be nice to get a deterministic answer that tty
p0 is connecting from 10.0.5.128, and tty p1 is connecting from
2001:470:1f00:546:2a0:c9ff:fe08:260a .
> Perhaps the programs that write to utmp/wtmp should just avoid writing
> hostnames? (although this is just a thought--I haven't tried to think
> through the implications of doing something like that)
Well, I could see that it may be useful to have a "snapshot" of what the
hostname was at the time the user originally connected - DNS records do
change, after all - but is there a good reason not to additionally store the
address?
=2D-=20
Kirk Strauser
--=-=-=
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQA/b4gr5sRg+Y0CpvERAhi5AJ97VGd1BTc0yUIEsGr0u+AfwDy7/wCfSwQ4
20Qcqpwvs9+UeGdiKqyLaE8=
=CmFG
-----END PGP SIGNATURE-----
--=-=-=--
More information about the freebsd-bugs
mailing list