On Thu, Jun 24, 2004 at 09:38:16AM -0400, Jack Howarth wrote: > Can anyone tell me if the following is expected behavior for > gnome? I noticed that under Fedora Core 2 if I lose internet > connectivity (ie pull the cable) that gnome terminal windows > will not open until I put it back on the ethernet. Is there a > workaround for this problem? > Jack > ps I think I also see this problem arise if the DNS servers go > down so I think it may be more related to a failure to do DNS > lookups for the machine itself. Unfortunately since the > machine connects with dhcp, I am unable to simply hard code the > domainname into the hosts file. Do you have an entry in /etc/hosts for localhost (127.0.0.1) and for the computer's host name and IP address? What I think is going on is: X is a network based client-server protocol. The server (display, keyboard, rodent) communicates over IP with the client (the program, in this case a terminal program). Obviously if the network fails, X has a problem. I have long argued that X should use the loopback interface (lo) rather than the actual ethernet interface for exactly this reason. I don't know to tell which interface X is using; perhaps someone who knows X better than I do can tell me. However, adding the computer's host name and loopback device to /etc/hosts is a good workaround. Unfortunately this means either static or pseudo-static IP addresses, or else some scripting I haven't gotten around to doing. -- Charles Curley /"\ ASCII Ribbon Campaign Looking for fine software \ / Respect for open standards and/or writing? X No HTML/RTF in email http://www.charlescurley.com / \ No M$ Word docs in email Key fingerprint = CE5C 6645 A45A 64E4 94C0 809C FFF6 4C48 4ECD DFDB
Attachment:
pgpijUMdqOzEd.pgp
Description: PGP signature
