Is there a way to get the exit code of a process run under a systemd scope
using systemd dbus API?
Thanks,
Mrunal
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
We are using systemd scopes in docker on RHEL.
As per advice on this list, we added Delegate=true to those scopes as we
are managing the cgroups under the scopes in custom code.
One thing that we are seeing is sometimes the value in cpu.cfs_period_us is
seemingly reset to -1 even though we write a
On Tue, Mar 15, 2016 at 10:01 AM, Michal Sekletar
wrote:
> On Tue, Mar 15, 2016 at 5:42 PM, Mrunal Patel wrote:
> >
> >
> >
> >> >
> >> > docker.io did that too three weeks ago:
> >> >
> >> > https://github.com/docker/doc
>
> > docker.io did that too three weeks ago:
> >
> > https://github.com/docker/docker/commit/65820132
>
> This seems odd. I thought you primarily want to enable delegation for
> scope units wrapping processes which constitute your container and not
> for the container manager itself. For example
On Tue, Mar 15, 2016 at 8:56 AM, Martin Pitt wrote:
> Michal Sekletar [2016-03-15 16:06 +0100]:
> > We had similar problem in the past with libvirtd and it got solved by
> > introducing Delegate option (man systemd.resource-control).
>
> docker.io did that too three weeks ago:
>
> https://githu
>
> >> 2. cpu.proc file itself goes missing especitally with the devices
> >> subsystemd even thought we mkdir the directory and write to the file.
> It is
> >> as if the file gets deleted by some other process.
>
> We had similar problem in the past with libvirtd and it got solved by
> introducing