On Tue, 04.11.14 16:10, Umut Tezduyar Lindskog (u...@tezduyar.com) wrote:
Hi Lennart,
Were you able to figure out the problem? You were suspecting that we
might not be getting cgroup empty notifications from kernel.
Finally fixed in git! It was a race in systemd-run itself, not in PID 1.
Hi Lennart,
Were you able to figure out the problem? You were suspecting that we
might not be getting cgroup empty notifications from kernel.
Umut
On Fri, Oct 24, 2014 at 3:19 PM, Umut Tezduyar Lindskog
u...@tezduyar.com wrote:
Hi,
Since you said you have covered my theories when you
Hi,
Since you said you have covered my theories when you implemented, I
have stopped looking in to this.
Following:
[root@axis-00408cc563e5 /mnt/flash/root]27929# cat stress
#!/bin/sh
systemd-run --scope /bin/true
systemd-run --scope /bin/true
systemd-run --scope /bin/true
systemd-run
On Mon, 29.09.14 15:34, Umut Tezduyar Lindskog (u...@tezduyar.com) wrote:
Hi,
I have stumbled on a race condition on systemd-run --scope command.
Due to race condition, unit might show up as active/running even
though there is no process in the cgroup.
Umut!
At the hackfest in Düsseldorf
Hi,
I have stumbled on a race condition on systemd-run --scope command.
Due to race condition, unit might show up as active/running even
though there is no process in the cgroup.
My best guess is we are missing the cgroup notification but when?
- Could it be that before systemd processes
