paging all socket geniuses
- From: Kenny <kentilton@xxxxxxxxx>
- Date: Tue, 29 Jul 2008 21:31:11 -0400
I sent the following to Franz but as you will see it does not look like anything to with anything other than how badly screwed up Windows, my laptop, or me or all three are... so what would you check first given the following? Does the computer name coming back instead of an IP address mean make-socket did not find... well, when I forgot to move the ethernet cable over it rightly complained specifically about the absence of a network... ah, but there is the local network and the Al Gore Superhighway. Well, I am too dumb on sockets even to tell the monkets what to try, any guesses welcome.
kt
The original query to Franz:
"On Tue, Jul 29, 2008 at 6:00 PM, Ken Tilton <kentilton@xxxxxxxxx> wrote:
:Deep in cl-s3, a Lisp interface to Amazon Simple Storage Solution, inside first the s-http-client package and then the s-sysdeps package, we have a call to:
0[6]: (ACL-SOCKET:MAKE-SOCKET :REMOTE-HOST "s3.amazonaws.com"
:REMOTE-PORT 80
:TYPE :STREAM
:ADDRESS-FAMILY :INTERNET)
0[6]: returned
#<MULTIVALENT stream socket connected from 192.168.2.160/2833 to 72.21.211.100/80 @ #x21aa6722>
That works fine on one XP machine and one Vista machine, and the distro I have generated runs on my brother's system, which I think is XP.
But on another XP of mine the call to make-socket goes away for almost a minute and then returns:
(SOCKET:MAKE-SOCKET :REMOTE-HOST "s3.amazonaws.com"
:REMOTE-PORT 80
:TYPE :STREAM
:ADDRESS-FAMILY :INTERNET)
1[4]: returned
#<MULTIVALENT stream socket connected from smokinjoe/1044 to
s3.amazonaws.com/80 @ #x21affe9a>
"smokinjoe" is the network name (terminology perhaps off) of the laptop. Anyway, the very long delay is to me a bad sign, and I am wondering if smokinjoe instead an IP address (again, pardon if my terminology off, this is not my field) is a reflection or cause or whatever of that.
After this a trace shows the cl-s3 family of code staggering on for a while before grinding to a hang on some attempted communication, but I can break out of it (the first time).
Side info: the laptop in question has no problem talking to the Internet, and again, this code runs fine on three systems I have tried.
I think the problem is obviously with my laptop and not ACL and would not normally bother you all, but I am wondering what the behavior of make-socket tells me, if anything. That would help my ongoing digging. In fact, if you just say, "Oh, that laptop must be badly corrupted" I will probably just forget the matter. My concern is that I am doing a roll-out now and wonder how many other people will have the same problem because of some oddity on their system."
.
- Follow-Ups:
- Re: paging all socket geniuses
- From: Tim Bradshaw
- Re: paging all socket geniuses
- From: alien_guy
- Re: paging all socket geniuses
- From: George Neuner
- Re: paging all socket geniuses
- From: D Herring
- Re: paging all socket geniuses
- From: Vilho Räisänen
- Re: paging all socket geniuses
- From: Stanisław Halik
- Re: paging all socket geniuses
- Prev by Date: Re: Diversion of the White Rabbit!
- Next by Date: Re: Generating normally distributed randoms in CL
- Previous by thread: Collecting like-labelled sublists of a list
- Next by thread: Re: paging all socket geniuses
- Index(es):
Relevant Pages
|