possible to have worker not accepting requests

[Bjørnar Ness]

Is it possible to have a worker process that does not answer http requests, but only works with
blocking stuff in a timer.at loop?

[Aapo Talvensaari]

On Thursday, 29 September 2016 22:56:18 UTC+3, Bjørnar Ness wrote:

Is it possible to have a worker process that does not answer http requests, but only works with
blocking stuff in a timer.at loop?

Run another instance of OpenResty?

[Bjørnar Ness]

On Friday, September 30, 2016 at 12:03:41 AM UTC+2, Aapo Talvensaari wrote:

Run another instance of OpenResty?

That was not the question, and I need shm

[Robert Paprocki]

Then no, it's not available. Can you use memcached or a similar storage engine instead of a shm?

[Bjørnar Ness]

Yeah.. I can ofcorse, but perhaps look at this as a feature request instead, then: block a worker from
accepting http requests and let it only run init_worker_by_lua_*  agentzh?

[Aapo Talvensaari]

On Friday, 30 September 2016 02:44:29 UTC+3, Bjørnar Ness wrote:

Yeah.. I can ofcorse, but perhaps look at this as a feature request instead, then: block a worker from
accepting http requests and let it only run init_worker_by_lua_*  agentzh?

I wouldn't wait for this happening anytime soon, or ever. Unless Nginx itself starts supporting something

that allows this. Maybe you should ask on Nginx mailing list about it. Currently workers are configured at

the top level of Nginx configuration.

You can still use another OpenResty with HTTP handlers and SHM and another OpenResty server that

loads SHM data through HTTP or stream from the other.