Liam Healy wrote:
>However, I cannot get CL-HTTP working there at all.  Whenever I try to
>start it up, it seems to make up a new, totally bogus IP number for
>the host it's on:
>[1998-01-24 19:40:29]  HTTP service enabled for: http://56.130.198.8:8000/
>Who knows where it's getting 56.130...?
Me too: I run linux 2.0.29 and recently tried CL-HTTP. Everytime I
started the server I got a different local IP address, all of them
completely different from the one that I gave to my machine. I took a
look at the code and finally got to the function that is supposed to
compute this address (www-utils:local-host-domain-name in
acl/server/unix.lisp), and it kept giving wrong answers when invoked
manually.
However, after starting the server it is really listening on port 8000
of the local machine.
>I thought maybe it was because I was at home and didn't have the ppp
>connection up at the time, so it couldn't reach the nameserver, but even
>when I dialed up and connected and then recompiled, I still got this
>behavior.  I doesn't have this problem on the SGI/ACL at work.
You don't need a nameserver to get your own local IP address. Evaluate
the function machine-instance and you should get your (correct) IP
address in what I suppose is network byte order. So it may be a problem
in the CL-HTTP code.
-Daniel
pd: Mr. Healy, how about submitting a bug report to
<AI.MIT.EDU? at Bug-CL-HTTP>