Mail Archives: cygwin/2005/04/09/05:41:50
>
>
>> There is a strange stuff, but it won't perturb me :
>> when i run my master/slaves programs, then run the testcase at the
>> same
>> time and kill it, the slave may have a socket read error if it was
>> reading on the socket at the same time that testcase is launched.
>
> I'm wondering if that's realy related or just a coincidence. Sockets
> have nothing to do with IPC, unless you're running on 9x, where the
> Cygserver/Client connection is done using sockets.
but it has to do with file descriptors.
I could reproduce it several time, each time the socket read error
occurs when the testcase is running.
It may not be an IPC issue, but a fork issue.
>
>> So i have to tune slave so i don't quit on socket read, but retry to
>> read on the socket, and it's fine, as the socket read will fail only
>> when the testcase is launched.
>
> What's the error code you get?
read just return less byte than expected, and it occurs only in this
case.
--
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/
- Raw text -