On Oct 25 15:06, Marcell Missura wrote: > I also find it weird that after an > error occured select() returns and tells you that the socket has something > to _read_.
That's documented standard behaviour. I pointed this out in my first reply. If you're still learning socket programming I'd like to suggest this book: http://www.amazon.com/Unix-Network-Programming-Vol-Networking/dp/0131411551/ref=sr_1_1/102-9342001-5959348?ie=UTF8&s=books&qid=1193321471&sr=8-1 It's the socket bible, sort of. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
