Hi,
I noticed that the --with-file-aio build option was removed in the following commit:
81bd2fa
NGINX supports --with-file-aio in its official builds, and some third-party NGINX modules expect this feature to be available because they are built against the standard NGINX source tree and build configuration.
Removing this option can therefore reduce compatibility with existing NGINX modules and make it more difficult to use OpenResty as a drop-in, modular alternative to standard NGINX builds.
I would suggest re-enabling --with-file-aio, or alternatively making it configurable, to improve compatibility with upstream NGINX and third-party modules.
Would you be open to reconsidering this change?
Hi,
I noticed that the --with-file-aio build option was removed in the following commit:
81bd2fa
NGINX supports --with-file-aio in its official builds, and some third-party NGINX modules expect this feature to be available because they are built against the standard NGINX source tree and build configuration.
Removing this option can therefore reduce compatibility with existing NGINX modules and make it more difficult to use OpenResty as a drop-in, modular alternative to standard NGINX builds.
I would suggest re-enabling --with-file-aio, or alternatively making it configurable, to improve compatibility with upstream NGINX and third-party modules.
Would you be open to reconsidering this change?