The default mode (Accept=no) expects your daemon to remain running forever
and handle *all* requests in the same instance. Basically once the daemon
is started and receives the listening socket, it continues working like a
traditional daemon would: start an event loop, perhaps use threads or
worker
Hello,
I am adding socket activation to a daemon. It basically works well, but for
multiple simultaneous connections, the systemd seems to serialize the
incoming requests, spawning the daemon for each request only after the
previous request is served (i.e. the daemon terminates).
Is it really the
Hi Team,
I have issue with SECLABEL into systemd udevadm 243 and I see that mainline
also have this issue.
It look like Yu forgot initialize data into commit:
25de7aa7b90 (Yu Watanabe 2019-04-25 01:21:11 +0200 924)
If I add something like:
SECLABEL{selinux}="some info"
to udev
On Wed, Mar 4, 2020 at 11:09 PM Matt Zagrabelny wrote:
> Hey Mantas,
>
> Thanks for the reply.
>
> On Wed, Mar 4, 2020 at 12:06 PM Mantas Mikulėnas
> wrote:
>
>> On Wed, Mar 4, 2020 at 7:26 PM Matt Zagrabelny
>> wrote:
>>
>>> Greetings,
>>>
>>> Do folks use non-root users to own AF_INET sockets
