On 2006-11-21 19:51:49 -0500, Douglas Tutty wrote: > On Wed, Nov 22, 2006 at 12:17:03AM +0100, Vincent Lefevre wrote: > > The machine should always have a FQDN, though it may be resolved > > locally only (in particular if your machine is not on a network). > > Otherwise you'll have problems with software that requests it (I > > don't think there's another portable way to fully identify the > > machine). > > I've had stand-alone (aka secure) boxes called localhost, with only > the standard 127.0.0.1 /etc/hosts entry. Never had a problem.
You haven't seen any problem, but this doesn't mean that there isn't any. For instance, the FQDN is useful for Message-Id generation, and a Message-Id should be correct, even locally. Now, /etc/hosts is not the only way to specify the FQDN, so perhaps your FQDN is correct after all. -- Vincent Lefèvre <[EMAIL PROTECTED]> - Web: <http://www.vinc17.org/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/> Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]