[Bug: 21.5-b27] open-network-stream-internal hangs if xemacs started before network brought up

[Stephen J. Turnbull]

>>>>> "Jan" == Jan Rychter <jan at rychter.com> writes:

    Jan> Andre Srinivasan:

    >> If I start xemacs before I bring up my network interface,
    >> open-network-stream-internal hangs on name resolution even
    >> though the network interface has subsequently been up.

I haven't a clue, but since nobody else seems at all interested, I'll
say that I need a little more localization than that.  IIRC (it's been
6 years since I last looked at this stuff) the networking code is a
labyrinth of platform-specific shims and special cases; I just don't
have time to go digging for stuff that ain't broke for me these days.

    Jan> (Firefox for example works just fine).

FWIW, Firefox (or anything in the Mozilla family) is about the last
app I would use as an example of how "only XEmacs" breaks, given the
huge amount of effort Mosaic/Netscape/Mozilla have put into working
around DNS issues in the last decade.


-- 
School of Systems and Information Engineering 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.