Core: added signal name to "signal process started" logging
wangxiaochen0 at gmail.com
Wed Dec 24 02:10:48 UTC 2014
On Sat, Dec 20, 2014 at 1:27 AM, Maxim Dounin <mdounin at mdounin.ru> wrote:
> On Thu, Dec 18, 2014 at 12:05:01PM +0800, Xiaochen Wang wrote:
>> It is useful to know which signal was sent to nginx master when we analyzed
>> error.log. If error_log level is warn/error/crit/alert/emerg, we could not
>> know this information from nginx master/worker error log.
> Adding more logging into signal process won't help, as signal
> process is not the only way to send signals to nginx. The main
> purpose of signal process is to allow sending signals on Windows,
> where there is no "kill" to do this.
Yes, you're right. This patch can only get message in signal process.
The signals sent from other process cannot be logged.
> Maxim Dounin
> nginx-devel mailing list
> nginx-devel at nginx.org
More information about the nginx-devel