On 8.7.2020 17.47, Chris PeBenito wrote:
I would like to implement a unit option that would make the seccomp
action SCMP_ACT_LOG so that I can test SystemCallFilter settings without
killing the services, like SELinux permissive mode.
I was reading this github issue about seccomp actions from
I would like to implement a unit option that would make the seccomp action
SCMP_ACT_LOG so that I can test SystemCallFilter settings without killing the
services, like SELinux permissive mode.
I was reading this github issue about seccomp actions from last year:
Dear Luke,
On 2020-07-08 13:10, Luke Alexander wrote:
> I had a look through some of the issues against the systemd github repo but
> could not find any matching - there were a couple which look promising but
> don't completely resolve our issue.
>
> Our issue is that we have a k8s (1.18,
Ah, no problem thanks for the info!
On Wed, Jul 8, 2020 at 12:17 PM Paul Menzel <
pmenzel+systemd-de...@molgen.mpg.de> wrote:
> Dear Luke,
>
>
> On 2020-07-08 13:10, Luke Alexander wrote:
>
> > I had a look through some of the issues against the systemd github repo
> but
> > could not find any
Hi,
I had a look through some of the issues against the systemd github repo but
could not find any matching - there were a couple which look promising but
don't completely resolve our issue.
Our issue is that we have a k8s (1.18, kube-router CNI) cluster comprised
of a number of Ubuntu 16.04
Am 08.07.20 um 11:01 schrieb Mkrtchyan, Tigran:
> Dear systemd developers,
>
> I failed to get the answer to my question from other sources, so
> here I am.
>
> We have a software that consist out of many components. Each component
> is a single service, let say A.service, B.service, C.service
Dear systemd developers,
I failed to get the answer to my question from other sources, so
here I am.
We have a software that consist out of many components. Each component
is a single service, let say A.service, B.service, C.service However,
often you want to be able to start and stop them
