To introduce systemd in our system, we've started with just wrapping rc
and all the old initscripts so we can get systemd running first and then
afterwards start converting to native services.
The boot is basically two services: legacy_rcS.service (which runs
/etc/init.d/rc S) and
I'm seeing a problem with a service sometimes failing to start due to a
missing cgroup.
After some debugging I've made the following observations:
After exec_spawn() forks, the child will set the sticky bit for the
cgroup (in cg_set_task_access) but sometimes, the cgroup is
I'm seeing a problem with a service sometimes failing to start due to a
missing cgroup.
After some debugging I've made the following observations:
After exec_spawn() forks, the child will set the sticky bit for the
cgroup (in cg_set_task_access) but sometimes, the cgroup is missing
Message-
From: systemd-devel-
bounces+anders.olofsson=axis@lists.freedesktop.org [mailto:systemd-
devel-bounces+anders.olofsson=axis@lists.freedesktop.org] On Behalf
Of Anders Olofsson
Sent: den 27 mars 2013 13:58
To: systemd-devel@lists.freedesktop.org
Subject: Re: [systemd-devel
: systemd-devel-
bounces+anders.olofsson=axis@lists.freedesktop.org [mailto:systemd-
devel-bounces+anders.olofsson=axis@lists.freedesktop.org] On Behalf
Of Anders Olofsson
Sent: den 26 mars 2013 13:43
To: systemd-devel@lists.freedesktop.org
Subject: [systemd-devel] Possible race condition
I'm seeing a problem with a service sometimes failing to start due to a missing
cgroup.
After some debugging I've made the following observations:
After exec_spawn() forks, the child will set the sticky bit for the cgroup (in
cg_set_task_access) but sometimes, the cgroup is missing (lstat
Hi,
I've got patches to solve tickets 56644 and 56874 that I would like to get
committed.
The patches are attached to the tickets but I'm guessing no one noticed them
there.
Could someone please have a look at them and either commit them or let me know
if they should be solved differently.
