Hi, On 2006-07-30 09:48:19 +0200, Ola Lundqvist wrote: > > Of course, the real problem is related to pump (it updates > > /etc/resolv.conf, but not /etc/hosts -- I should probably > > use a wrapper). > > The reason for that is that as far as I know, no software should > update the /etc/hosts file (maybe). I do not know.
This wouldn't solve all the problems anyway: the connection with the current VNC viewer would freeze as soon as the IP address changes, even though /etc/hosts were updated. Even though the VNC server says that the display is <hostname>:1, this doesn't mean that one should connect to <hostname>. If one knows that the connection is local, one should connect to the loopback interface (which is the default when the hostname isn't given to the VNC viewer). Now, perhaps that if the IP address associated to the Ethernet interface can change (e.g. because the machine is a laptop that moves from network to network), the hostname should resolve to 127.0.0.1, to avoid problems with software that would force a connection to <hostname>. -- 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 / SPACES project at LORIA
