Re: SOCKET-SERVER bug?

[Paolo A. <am...@mc...>]

On Fri, 19 May 2000 10:30:46 +0200 (MET DST), Bruno Haible <ha...@il...>
wrote:

> Paolo, your machine *is* misconfigured.

Yes it is. I was finally able to find and fix the problem.


> > uname({sys="Linux", node="localhost.localdomain", ...}) = 0
> 
> This is already rather fishy.
[...]
> Your machines tries to access two other machines (195.110.128.1, 193.204.5.62)
> on port 53 (see /etc/services for what that means). Fix your config files!

Guess what? Those other machines are my ISP's primary and secondary name
servers :)

Here is what may have happened. My Red Hat Linux shipped with the default
host name localhost.localdomain, which I never changed. When the networking
software tried to resolve that bogus name, it reached for DNS but wasn't
able to contact the name servers because I was offline.

I changed the name to localhost with the hostname program and the problem
went away:

[1]> (socket-server)
#<SOCKET-SERVER 127.0.0.1:1025>
[2]> (socket-server 12345)
#<SOCKET-SERVER 127.0.0.1:12345>
[3]> 


Paolo

P.S.
Sorry for dumping to you over 40K worth of strace output.
-- 
EncyCMUCLopedia * Extensive collection of CMU Common Lisp documentation
http://cvs2.cons.org:8000/cmucl/doc/EncyCMUCLopedia/