strange problem with nonblocking sockets
From: anki (ankisharma_at_gmail.com)
Date: 02/28/05
- Next message: Eric Sosman: "Re: calling my custom function same as library function"
- Previous message: Flash Gordon: "Re: Required stack size"
- Next in thread: Thomas Matthews: "Re: strange problem with nonblocking sockets"
- Reply: Thomas Matthews: "Re: strange problem with nonblocking sockets"
- Reply: Jens.Toerring_at_physik.fu-berlin.de: "Re: strange problem with nonblocking sockets"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 28 Feb 2005 06:03:13 -0800
hi
I am getting a strange problem when using non-blocking sockets. I
have a application which listens on port 3333. Now i try to connect to
it. connection is succesful. No problem.
But when i start the client first and then the server, server is not
able to bind on port 3333.
when i did netstat -a | grep 3333
tcp 0 0 lab123.exl:3333 lab123.exl:3333 ESTABLISHED
I am working on Red hat linux.
Thanks in advance
bye
anki
- Next message: Eric Sosman: "Re: calling my custom function same as library function"
- Previous message: Flash Gordon: "Re: Required stack size"
- Next in thread: Thomas Matthews: "Re: strange problem with nonblocking sockets"
- Reply: Thomas Matthews: "Re: strange problem with nonblocking sockets"
- Reply: Jens.Toerring_at_physik.fu-berlin.de: "Re: strange problem with nonblocking sockets"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|