On Mon, 17 Jul 2017, Risto Vaarandi wrote:
that is an interesting problem. Let me ask the following question -- is the
restart done via system init script? If so, the behavior you are observing
might be caused by the init script -- it initially sends a TERM signal to
the sec process which is
Hi Risto,
that's quite exactly my impression as well.
I've been experimenting with
KillMode (process vs. cgroup)
KillSignal
TimeoutStopSec
Type (simple without --detach vs. forking with --detach)
and some other settings in the unit file. Systemd just sometimes wants to send
KILL
hi Peter,
I did more testing on Centos7 and was able to run into the same issue.
Unfortunately, this problem reappeared once even with "SendSIGKILL=no"
setting :-( It appears that a similarly looking bug has been reported
before for an earlier version of systemd, but that was a while ago:
hi Peter,
that is an interesting problem. Let me ask the following question -- is the
restart done via system init script? If so, the behavior you are observing
might be caused by the init script -- it initially sends a TERM signal to
the sec process which is then followed by KILL, since the
Hello Mr. Eckel:
In message <5e1c2184-2b8f-4d7a-a8f2-970a0bdbe...@eckel-edv.de>,
Peter Eckel writes:
>I think I found a bug (or a mistake in the documentation) in SEC.
Possibly.
>The manpage says:
>
>> SEC_SHUTDOWN - generated when SEC receives the SIGTERM signal, or
>> when SEC reaches all
Hi Risto,
I think I found a bug (or a mistake in the documentation) in SEC.
The manpage says:
> SEC_SHUTDOWN - generated when SEC receives the SIGTERM signal, or when
> SEC reaches all EOFs of input files after being started with the --notail
> option. With the --childterm option, SEC
