Welcome! Log In Create A New Profile

Advanced

SIGIO only mean readable or writable, how channel event avoid writable

Posted by yang chen 
[image: 内嵌图片 1]

in the "Linux System Programming: Talking Directly to the Kernel and C
Library", it says SIGIO mean readable or writable, and in man page it says
SIGIO means I/O is possible on a descriptor,
so if this, I'm curious that channel is writable, nginx will receive the
SIGIO?
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Attachments:
open | download - image.png (314.4 KB)
Hi!

The channel, on the worker process land, is readonly, since the write end
was closed.

For the SIGIO, which is just ignored by the worker while just affects a
global variable ngx_sigio on the master land, though it is never used.

However, for generating the signal SIGIO, you shall call the fcntl and set
the asynchronous mode, but the master doesn’t do that.

So i think SIGIO will not be passed when the channel is writable, please
correct it if anywhere is improper :)


On 13 November 2017 at 00:39:08, yang chen (shanchuan04@gmail.com) wrote:

[image: 内嵌图片 1]

in the "Linux System Programming: Talking Directly to the Kernel and C
Library", it says SIGIO mean readable or writable, and in man page it says
SIGIO means I/O is possible on a descriptor,
so if this, I'm curious that channel is writable, nginx will receive the
SIGIO?
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Attachments:
open | download - ii_15fb112fdac2408c (314.4 KB)
Sorry, only registered users may post in this forum.

Click here to login