If you send a SIGINT signal to Syslog-ng, it issues the message SIGTERM received, terminating Looking at the code, it uses the same code for both SIGTERM and SIGINT. I suggest the message be reworded as SIGTERM or SIGINT received, terminating -- Bryan Henderson San Jose, California
On Mon, 2007-02-26 at 03:26 +0000, Bryan Henderson wrote:
If you send a SIGINT signal to Syslog-ng, it issues the message
SIGTERM received, terminating
Looking at the code, it uses the same code for both SIGTERM and SIGINT. I suggest the message be reworded as
SIGTERM or SIGINT received, terminating
I've just committed this patch: --- orig/src/main.c +++ mod/src/main.c @@ -176,7 +176,7 @@ main_loop_run(GlobalConfig *cfg) } if (sig_term_received) { - msg_notice("SIGTERM received, terminating", NULL); + msg_notice("Termination requested via signal, terminating", NULL); sig_term_received = FALSE; break; } -- Bazsi
On Mon, 2007-02-26 at 03:26 +0000, Bryan Henderson wrote:
If you send a SIGINT signal to Syslog-ng, it issues the message
SIGTERM received, terminating
Looking at the code, it uses the same code for both SIGTERM and SIGINT. I suggest the message be reworded as
SIGTERM or SIGINT received, terminating
Fixed this with a less technical explanation: msg_notice("Termination requested via signal, terminating", NULL); This covers both cases. -- Bazsi
participants (2)
-
Balazs Scheidler
-
bryanh＠giraffe-data.com