Nginx-0.6.32

Server NGINX
21

“Igor S.” [email protected] wrote in message
news:[email protected]…

What I see in log is that some/one(thing) has sent -TERM to master:
2008/07/09 19:23:21 [notice] 54095#0: signal 15 (SIGTERM) received,
exiting

Yes I noticed that, however I cannot think right now, what could send
TERM
to nginx. Anyway I’ll try once more tracking this strange problem.

Thanks Igor.
Athan

22

Athan D. ha scritto:

Athan

You can use the attached patch.
It adds support for POSIX extended signal handlers, so that it is now
possible to know the signal sending process ID (and the real user ID,
but I don’t show this info in the log).

Note that the patch is not well tested, and I’m not sure it will compile
without problems on all systems supported by Nginx (the system must be
XSI compliant, too), so don’t use in production.

I have tested in on Debian Lenny.

Manlio P.

23

“Manlio P.” [email protected]
wrote in message news:[email protected]…

You can use the attached patch.
It adds support for POSIX extended signal handlers, so that it is now
possible to know the signal sending process ID (and the real user ID,
but I don’t show this info in the log).

Thanks Manlio, I’ll give it a try if everything else fail.

Athan

24

Manlio P. ha scritto:

I have tested in on Debian Lenny.

Correction: the log message should be:

ngx_log_error(NGX_LOG_NOTICE, ngx_cycle->log, 0,
"signal %d (%s) received from %d%s ", signo,
sig->signame, info->si_pid, action);

Manlio P.