Xref: utzoo gnu.emacs.help:934 comp.emacs:9921
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!tut.cis.ohio-state.edu!AI.MIT.EDU!tadtec!tjfs
From: tadtec!tjfs@AI.MIT.EDU (Tim Steele)
Newsgroups: gnu.emacs.help,comp.emacs
Subject: Strange behaviour of open-network-stream
Message-ID: <9101211145.AA07912@tadtec.uucp>
Date: 21 Jan 91 11:45:43 GMT
Sender: daemon@tut.cis.ohio-state.edu
Followup-To: gnu.emacs.help
Organization: Gatewayed from the GNU Project mailing list help-gnu-emacs@prep.ai.mit.edu
Lines: 23

A strange thing...

On our Unix system (TP-IX/68K 1.23 which is based on AT&T V.3.2) the
function open-network-stream hangs in the function gethostbyname().
sdb indicates that the hang is occurring in res_send.c (internal to
gethostbyname) after it has done a select() which indicates there is a
packet of data returned by named; it then does a recv() which hangs.

Further investigation shows that killing the name daemon named makes
it work OK.  A vanilla gethostbyname("valid-host") inserted just
before the proper gethostbyname() also hangs, so there's nothing wrong
with the argument.  A dummy program which just does a
gethostbyname("same-host") works OK, as do all the network utilities
which are built with the same library.

Hitting ^G during the hang causes gethostbyname() to return *with the
right answer*, but then Emacs aborts the function (of course).

Any ideas?

Thanks!

Tim