On Thu, 15 Jul 1999, Taral wrote:
> Okay, who can tell me why this code doesn't issue a SIGIO on connect?
>
> Taral
>
> --- cut here ---
[...]
> listen(s,0);
[...]
a) I don't know to what extent async io is supported by sockets esp. when
it comes to incoming connections. Let's assume it is supported.
b) The second argument of listen tells the kernel how many incoming
connections in non connected, 'embryonic' state it shall handle. This
it the size of the incoming queue buffers which are required as several
SYN packets have to be exchanged with the possible connector before a
connection is established and an accept() can actually succeed.
It is typical for many UNIX implementation to ignore this argument, or
at least use some minimum buffers, or a system default when 0 is given,
although the standards don't allow for that.
Linux used to take it literally, as the standards require, at least
when I last did such things with linux.
This means, you allow at most 0 incoming connections in embryonic
state. It seems not very surprising to me that you don't receive any
SIGIO's upon connection attempt.
If this does not help, see a) and dig in deeper there.
Michael.
--
Michael Weller: [EMAIL PROTECTED], [EMAIL PROTECTED],
or even [EMAIL PROTECTED] If you encounter an eowmob account on
any machine in the net, it's very likely it's me.
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
