> Yeah. Well, grab the source and see what it's doing, but also check
> the value in the notify_on_release file in
> /sys/fs/cgroup/systemd// and further sub-directories.
I think this all may be due to the older software versions available
on Fedora 17. Using systemd 197 and lxc 0.8.0 under Arch
Quoting Lars Kellogg-Stedman (l...@oddbit.com):
> > No idea about the systemd aspects, but the best way to get those cgroups
> > to be autoremoved is using a release_agent. See
> > Documentation/cgroups/cgroups.txt in the kernel source.
>
> Serge,
>
> Thanks for the pointer. That does seem like
> No idea about the systemd aspects, but the best way to get those cgroups
> to be autoremoved is using a release_agent. See
> Documentation/cgroups/cgroups.txt in the kernel source.
Serge,
Thanks for the pointer. That does seem like the right direction,
although it looks like this cgroup hiera
> banging my head against LXC for a bit today. My latest problem is that
> if a container fails to start, I run into this situation:
>
> # lxc-start -n node0
> lxc-start: Device or resource busy - failed to remove previous cgroup
> '/sys/fs/cgroup/systemd/node0'
> lxc-start: failed to spawn
Quoting Lars Kellogg-Stedman (l...@oddbit.com):
> I'm runing LXC 0.7.5 under Fedora 17 (3.7.3-101.fc17.x86_64). I've been
> banging my head against LXC for a bit today. My latest problem is that
> if a container fails to start, I run into this situation:
>
> # lxc-start -n node0
> lxc-start:
I'm runing LXC 0.7.5 under Fedora 17 (3.7.3-101.fc17.x86_64). I've been
banging my head against LXC for a bit today. My latest problem is that
if a container fails to start, I run into this situation:
# lxc-start -n node0
lxc-start: Device or resource busy - failed to remove previous cgroup
