@linuxmaniac
Well, actually systemd does not restart Kamailio in case of segfault.
Just verified this on my system (Debian 9 "stretch").
So I would really want this change merged. For now I manually changed my
systemd configuration to "on-failure".
--
You are receiving this because you are
I still don't see why we need this. What is the case of "non null exit"?
>From my POV I only want kamailio service to restart if there was a segfault
>and AFAICT that is already happening with the actual systemd configuration
--
You are receiving this because you are subscribed to this thread.
@linuxmaniac - any spare time soon to review and decide what to do with this PR?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@linuxmaniac we can also mark exit code for broken config as SuccessExitStatus.
Than unit will not restart in case of broken config
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@linuxmaniac yes, unit will be restarted infinity, Rate of restarts may limiter
using "RestartSec" keyword
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
What happens if you have a non-working config and you have `on-failure`? I
would assume the daemon will be restarted forever
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
See my comment at
https://github.com/kamailio/kamailio/issues/1085#issuecomment-296592791
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@linuxmaniac - are you ok with the changes proposed for deb packaging regarding
the systemd?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
