FYI:
I tried to simply bypass the pending job check:
+int ignore_stop_pending = true;
static void socket_enter_running(Socket *s, int cfd) {
...
-if (unit_stop_pending(UNIT(s))) {
+if (!ignore_stop_pending && unit_stop_pending(UNIT(s))) {
But, as expected, it's not as that easy -
Uoti,
yes, it was about Redhat/Centos7 authd (rfc 1413) service, so it was
the latter - one child process per each connection:
auth@.service:[Unit]
auth@.service:Description=Authd Ident Protocol Requests Server
auth@.service:After=local-fs.target
auth@.service:
auth@.service:[Service]
-Original Message-
From: Lennart Poettering [mailto:lenn...@poettering.net]
Sent: Monday, 29 May, 2017 17:45
To: Moravec, Stanislav (ERT) <stanislav.mora...@hpe.com>
Cc: systemd-devel@lists.freedesktop.org
Subject: Re: [systemd-devel] socket unit refusing connection when JOB_STOP is
p
No one has any opinion?
Thanks again
Stan
-Original Message-
From: systemd-devel [mailto:systemd-devel-boun...@lists.freedesktop.org] On
Behalf Of Moravec, Stanislav (ERT)
Sent: Tuesday, 16 May, 2017 13:28
To: systemd-devel@lists.freedesktop.org
Subject: [systemd-devel] socket unit
Hello all,
I wanted to seek your opinion about correctness of the current behavior
of socket activated units.
Let's assume we have socket activated service (for example authd - auth.socket)
and
some other background service (for the purpose of this test called
authtest.service)
that needs to
