[En-Nut-Discussion] TCP/socket timeouts without effect

[Jean Pierre Gauthier]

Sorry Oliver,
Don't waste time about this,
"timeout bug" was mine and only due to the difference between send/receive
return value between unix (-1 on timeout) and Nut/OS (0 on timeout as
specified). No link with Nut/OS release. 
... the current focus is about 'numerous LASTACK' now. 
Jean Pierre


-----Message d'origine-----
De : en-nut-discussion-bounces at egnite.de
[mailto:en-nut-discussion-bounces at egnite.de] De la part de Oliver Schulz
Envoyé : dimanche 13 juin 2004 23:43
À : Ethernut User Chat (English)
Objet : AW: [En-Nut-Discussion] TCP/socket timeouts without effect

Hi Jean Pierre,

AFAIK there was no change in the timeout handling from version 3.4.1 to
3.4.2.

Which version did you use before migration?

Anyway, I will check the timeouts for sending and receiving.

Cheers,
Oliver.

> -----Ursprüngliche Nachricht-----
> Von: en-nut-discussion-bounces at egnite.de
> [mailto:en-nut-discussion-bounces at egnite.de]Im Auftrag von Jean Pierre 
> Gauthier
> Gesendet: Freitag, 11. Juni 2004 06:33
> An: 'Ethernut User Chat (English)'
> Betreff: RE: [En-Nut-Discussion] TCP/socket timeouts without effect
> 
> 
>  
> Hello Nuts-addicted workers,
> Since migration to Nut/OS 3.4.2, TCP/socket  timeouts (on
> receive/emit) seem
> to have no effect here (set by NutTcpSetSockOpt and SO_SNDTIMEO 
> SO_RCVTIMEO
> options) . They well worked with previous Nut/OS release. 
> I compiled some new tcp/time files sources without effect too (perhaps 
> the good file to compile lacks...).
> Anyone has experienced the same thing?
> Jean Pierre
> 
> _______________________________________________
> En-Nut-Discussion mailing list
> En-Nut-Discussion at egnite.de
> http://www.egnite.de/mailman/listinfo.cgi/en-nut-discussion
> 
_______________________________________________
En-Nut-Discussion mailing list
En-Nut-Discussion at egnite.de
http://www.egnite.de/mailman/listinfo.cgi/en-nut-discussion