About ssl support of nginx

Server NGINX
1

we use “–with-http_spdy_module --with-http_ssl_module
–with-openssl=$(ROOTDIR)/deps/openssl-$(V_OPE NSSL)
–with-openssl-opt=darwin64-x86_64-cc” to embed ssl support into nginx
in
macos system , but we find that “./config” which is in the file of
nginx/auto/lib/openssl/make doesn’t make action, but “./Configure” can
be
run successfully.

So, is it the problem of nginx or openssl, in my option, ssl doesn’t
take
macos into account for embedded nginx.

Posted at Nginx Forum:

2

Hello!

On Wed, May 13, 2015 at 10:26:07PM -0400, hy05190134 wrote:

we use “–with-http_spdy_module --with-http_ssl_module
–with-openssl=$(ROOTDIR)/deps/openssl-$(V_OPE NSSL)
–with-openssl-opt=darwin64-x86_64-cc” to embed ssl support into nginx in
macos system , but we find that “./config” which is in the file of
nginx/auto/lib/openssl/make doesn’t make action, but “./Configure” can be
run successfully.

So, is it the problem of nginx or openssl, in my option, ssl doesn’t take
macos into account for embedded nginx.

There are two basic options:

  • define KERNEL_BITS environment variable to 64 to instruct OpenSSL’s
    ./config to do the right thing;

  • build OpenSSL yourself with any options you want (or, e.g.,
    install one from MacPorts), and then instruct nginx to use
    appropriate headers and library files using the “–with-cc-opt”
    and “–with-ld-opt” configure options.

–
Maxim D.
http://nginx.org/

3

thanks a lot, I will try for your suggestions.

Posted at Nginx Forum:

4

I fork + exec child processes and I would like to get some kind of
notification when they exit. However, the nginx signal handler reaps my
child processes and logs a message like

2015/05/14 14:12:24 [notice] 28033#0: signal 17 (SIGCHLD) received
2015/05/14 14:12:24 [notice] 28033#0: unknown process 28044 exited with
code 1

Nginx knows that this process isn’t one of its own children- is there
some way I can either register interest in my child process, or get an
event sent to me somehow on child exit?

FWIW, I’m using nginx-1.7.7 with the ngx_lua extension on an older
RedHat server.

Thanks

Erik

5

J.J J wrote on Sunday, May 17, 2015 2:54 AM

Signal handler is ngx_signal_handler which in worker process does
nothing but log exit code and release possible holded mutexes,
only master process reap child by setting ngx_reap to 1 and spawn
it in ngx_reap_children if registed in ngx_processes(worker, loader, manager)

So no, you can’t, but you can implement this logic yourself.

Understood, thanks. I guess I’ll just add a --no-reap-unknown command
line argument to suppress reaping of unknown processes.

6

Signal handler is ngx_signal_handler which in worker process does
nothing
but log exit code and release possible holded mutexes, only master
process
reap child by setting ngx_reap to 1 and spawn it in ngx_reap_children if
registed in ngx_processes(worker, loader, manager)

So no, you can’t, but you can implement this logic yourself.

On Fri, May 15, 2015 at 9:22 PM, Nelson, Erik - 2 <
[email protected]> wrote:

sent to me somehow on child exit?
may contain information that is privileged, confidential and/or proprietary
and subject to important terms and conditions available at
Terms and Conditions for Electronic Communications. If you are not the
intended recipient, please delete this message.

nginx mailing list
[email protected]
nginx Info Page

–
居佳佳

以上