Hi,
I'm a bit confused about the kill signals in rsyslog 7.2.1. In the manual
says "TERM , INT, QUIT Rsyslogd will die." However, it seems that only
QUIT actually works, which confuses the init scripts, at least in CentOS
6.3, eventually leading to the init script doing kill -9, which is bad.
I've done the following debugging using strace rsyslogd -d -n -f
/etc/rsyslog.conf
Sending kill -TERM:
) = ? ERESTARTNOHAND (To be restarted)
--- SIGTERM (Terminated) @ 0 (0) ---
rt_sigreturn(0xf) = -1 EINTR (Interrupted system
call)
select(1, NULL, NULL, NULL, {86400, 0}
Sending kill -INT:
) = ? ERESTARTNOHAND (To be restarted)
--- SIGINT (Interrupt) @ 0 (0) ---
rt_sigreturn(0x2) = -1 EINTR (Interrupted system
call)
select(1, NULL, NULL, NULL, {86400, 0}
Sending kill -QUIT:
) = ? ERESTARTNOHAND (To be restarted)
--- SIGQUIT (Quit) @ 0 (0) ---
write(1, "5495.499530531:7f9d0571e740: DoD"...,
435495.499530531:7f9d0571e740: DoDie called.
) = 43
<Lots of more output>
Is this intended behaviour? If so, I could change my init script, but the
man page should be updated then.
Regards,
/Martin
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE
THAT.
