[7826] in athena10
Re: nss-myhostname
daemon@ATHENA.MIT.EDU (Jonathan Reed)
Sun Jul 10 21:04:15 2011
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=windows-1252
From: Jonathan Reed <jdreed@MIT.EDU>
In-Reply-To: <alpine.DEB.2.02.1107102010250.30450@dr-wily.mit.edu>
Date: Sun, 10 Jul 2011 21:04:04 -0400
Cc: Geoffrey Thomas <geofft@mit.edu>, debathena@mit.edu
Message-Id: <B60193DA-4DCF-464E-9202-93EAE14F1BF6@mit.edu>
To: Anders Kaseorg <andersk@mit.edu>
Content-Transfer-Encoding: 8bit
==, for the most part. AFAICT, it's useful for a sufficiently small subset of our users that we should document its existence and when to use it, but not add it to any metapackages. Is this relevant for #245?
-Jon
On Jul 10, 2011, at 8:14 PM, Anders Kaseorg wrote:
> On Sun, 10 Jul 2011, Geoffrey Thomas wrote:
>> It seems likely that we want this. It will handle the machine's hostname/IP
>> changing, but also not return 127.x.x.x unless the machine is simply not on
>> the network.
>
> What do you believe we want this for? Cluster machines have a static IP.
> For laptops with a dynamic IP, it’s more correct for their hostname to
> resolve to 127.0.1.1, so that loopback connections don’t break every time
> the machine goes off the network. (And we shouldn’t fiddle with the
> network config of non-cluster machines, especially if it ain’t broke.)
>
> Anders
