Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

socket closing question



FRamsay at castelhq.com writes:

> I should probably clarify, the local application did not close the socket,
> but neither did the remote application.

What kind of socket, anyways?  SOCK_STREAM/TCP?

Is SO_KEEPALIVE set on this socket?  (note: this probably has nothing
to do with your problem)

> And yet the socket did close.  So I'm trying to figure out where the socket
> originally closed and from there
> why the socket closed.

Can you reproduce this easily?  Can you trace what's going on on the
wire with tcpdump or Ethereal?  

If you're using TCP, what is the relevant output of "netstat proto
tcp" on the two machines?

Can you trace what is going on with tcpdump?  If you're using UDP or
something else, this could be useful as well.  Sending us the relevant
output of tcpdump would be infinitely useful here...


Regards,

--kevin
-- 
Kevin D. Clark (kclark at CetaceanNetworks.com)
ADVERTISEMENT:  On Sunday May 4th, I'm riding my bicycle 100 miles
in the American Diabetes Association's Tour de Cure ride.  If you're
interested in sponsoring me, please send me email.





BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org