Hi,
I have an application which connects via a network socket to a server
running on the same machine (IP 127.0.0.1) This application uses the
function 'select' to wait for new data from the server or until a two
seconds timeout. This works well until there is network traffic on the
external network interfaces (eth* or WLAN). When there is network
traffic on the external interfaces, the select function does not wait
anymore but it returns with a return code of zero, indicating not data
available on the socket. This happens nearly immediately (after 8 to 9
microseconds) and not after the specified two seconds interval. The
timeout parameter of select is updated accordingly (it shows eg. 1 s
999991 us).
Up to now I could not test this with another kernel but I will try to do
it this afternoon. Are there any known problems with select? Is there
any way to circumvent this?
Any help would be greatly appreciated!
Jürgen
--
Jürgen Mell (Software-Entwicklung) mell@xxxxxxxxxxxxxxxxxxx
Tel.: +49-511-762-18226 http://www.hedrich-winding.com
FAX : +49-511-762-18225
Mobil: +49-160-7428156
----------------------------------------------------------------------------
HEDRICH winding systems GmbH
An der Universität 2 (im PZH)
D-30823 Garbsen (GERMANY)
----------------------------------------------------------------------------
Geschäftsführer: Karsten Adam
Handelsregister: Wetzlar, HRB 4768
Steuernr.: 020/235/20110 USt-IdNr.: DE 258258279
----------------------------------------------------------------------------
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
