>>>> "Jan" == Jan Rychter
Jan> ... at which points XEmacs becomes totally unresponsive and
Jan> stays in that state forever (as far as I can tell). There is
Jan> no other network activity occurring.
If this is XEmacs hanging, and not the system call failing to timeout,
then I would say it's Gnus breakage (inflooping on an operation known
to have failed), not XEmacs itself. OTOH, your resolver setup is
apparently broken. It is supposed to read resolv.conf on every call
AFAIK---changes to resolv.conf should take effect immediately.
Anyway, they do for me.
One thing you can do is to use a caching nameserver locally. You
don't need bind, just something small like pdnsd.
Jan> What I don't understand is why the lookup doesn't just
Jan> fail. XEmacs shouldn't hang forever, no matter what happens.
If Gnus gets into a tight loop, there's not much we can do about it.
Maybe we can add some checks for QUIT so at least you can C-g out of it.
Jan> So, it seems my hangs are directly related to the resolver
Jan> (no DNS servers being reachable) and should be easily
I'll see what I can do about checking this. Thanks for the analysis!
Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.