%% Dominik Vogt <dominik_vogt_at_hp.com> writes:
dv> No it's not fvwm2. It's the X server that is hanging. The fvwm2 line
dv> in my .xinitrc hasn't even been touched when it hangs.
Oh. _That_ almost certainly means your networking is set up incorrectly
on your system somehow. X hangs waiting for some network system call to
timeout, most likely gethostbyname(): a DNS lookup maybe? Does this
happen when you have a valid network connection, or only when you don't?
If the former, I dunno! :) If the latter, check your /etc/hosts file,
for example, to make sure the hostname of your system appears there
(maybe with 127.0.0.1?). If so, you should go follow the path from your
gethostbyname man page to find out how your system does
hostname-to-address lookups; depending on whether you're using DNS, NIS,
NIS+, etc. it can be done very differently. Anyway, make sure that it
looks in /etc/hosts _first_, before DNS or NIS; that way (I think) if
your network is not "up" (PPP is not connected or whatever) it will
still find the hostname in /etc/hosts and won't punt.
HTH.
--
-------------------------------------------------------------------------------
Paul D. Smith <psmith_at_baynetworks.com> Network Management Development
"Please remain calm...I may be mad, but I am a professional." --Mad Scientist
-------------------------------------------------------------------------------
These are my opinions---Nortel Networks takes no responsibility for them.
--
Visit the official FVWM web page at <URL: http://fvwm.math.uh.edu/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Tue Feb 16 1999 - 10:10:01 GMT