On Tue, 04.03.14 16:23, Jacek Pielaszkiewicz (j.pielasz...@samsung.com) wrote:
> +-machine.slice > │ L-machine-lxc\x2dtizen\x2dbash\x2d2.scope > │ +-2672 /usr/libexec/libvirt_lxc --name tizen-bash-2 --console 20 -- > security= > │ L-machine.slice > │ L-machine-lxc\x2dtizen\x2dbash\x2d2.scope > │ L-system.slice > │ +-2681 /usr/lib/systemd/systemd > │ +-systemd-logind.service > │ │ L-3215 /usr/lib/systemd/systemd-logind > │ +-connman.service > │ │ L-3214 /usr/sbin/connmand -n > │ +-dbus.service > │ │ L-3212 /usr/bin/dbus-daemon --system --address=systemd: -- > nofork --n > │ +-console-getty.service > │ │ L-3240 /sbin/agetty --noclear -s console 115200 38400 9600 > │ +-wpa_supplicant.service > │ │ L-3241 /usr/sbin/wpa_supplicant -u > │ L-systemd-journald.service > │ L-3200 /usr/lib/systemd/systemd-journald OK, this looks wrong, the machine slice appears to have been used twice in the cgroup path. Can you try this with 210 in the container, and then run "systemctl show" and report the value of the ControlGroup property, please? If you boot this up with npsawn instead of libvirt-lxc, does t work then? Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
