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 | Linux Links | Bling | About BLU

BLU Discuss list archive


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

send problem



[Derek D. Martin: Tue, May 28, 2002 at 05:32:07PM -0400]
> 
> Remember, UDP is a connectionless protocol -- it does not guarantee

he's using TCP. (ESTABLISHED, FINWAIT_2, etc are TCP states).

the reason step 2 doesn't generate an error is due to his send
buffers. This is a race condition anyhow - many sends will generate
vaild packets that will generate resets - but the rst won't arrive
until you have returned from the system call. If you want
semi-immediate error notification you should poll() with POLLIN and
read the eof or POLLERR.

-P




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