> Okay, who can tell me why this code doesn't issue a SIGIO on connect? Without you giving kernel revisions nobody for all cases > int fl = fcntl(s,F_GETFL); > fcntl(s,F_SETFL,fl|O_ASYNC); > fcntl(s,F_SETSIG,SIGIO); // Just in case no set owner > listen(s,0); 0 means "zero connections backlogged" - undefined behaviour and accept on connect is a 2.0.3x (x=4 I think) fix - To unsubscribe from this list: send the line "unsubscribe linux-net" in the body of a message to [EMAIL PROTECTED]
- No SIGIO on connect? Taral
- Re: No SIGIO on connect? Dr. Michael Weller
- Re: No SIGIO on connect? Taral
- Alan Cox
