Martin Buchholz wrote:
>>>>> "Ben" == Ben Wing <ben(a)666.com> writes:
Ben> please investigate and see if there's an obvious solution, e.g. different
Ben> params. if not, perhaps we should declare getaddrinfo[] broken on RH 6.0
Ben> [perhaps it's fixed in later versions]. the way to do this is to put
something
Ben> like
Ben> #undef BROKEN_GETADDRINFO
Ben> into config.h, and then have configure test for Red Hat 6.0 and turn the define
Ben> on. [even better, you could make a proper configure test! have configure run a
Ben> little program that calls getaddrinfo[], then waits 30 seconds or until it
Ben> dies. if it's still around 30 seconds later, kill the program and define
Ben> BROKEN_GETADDRINFO. maybe the timeout should be longer, for modem users?]
Ben> martin, you're the configure expert; want to write this support?
Not until we get a handle on what the problem could be. It's very
hard to believe that Red Hat 6.0 is simply broken, because *I* was
using it (and many other people besides).
Debugging may find a problem on Alastair's system, and that could be
the incentive for inadequate error checking in the XEmacs source code.
The obvious thing to try is to temporarily stop using things like a
local `named', and see when things start working again.
agreed -- although getaddrinfo[] is hardly necessary [no one really has ipv6
networks yet!], and it looks very bad when we just hang indefinitely at
startup. perhaps we should just set a 30-second timer when we call this
function, and forcibly longjmp[] if we get stuck, outputting a warning message
to stderr.
Martin
--
Ben
In order to save my hands, I am cutting back on my mail. I also write
as succinctly as possible -- please don't be offended. If you send me
mail, you _will_ get a response, but please be patient, especially for
XEmacs-related mail. If you need an immediate response and it is not
apparent in your message, please say so. Thanks for your understanding.
See also
http://www.666.com/ben/chronic-pain/