This bug was fixed in the package systemd - 228-1ubuntu2
---
systemd (228-1ubuntu2) xenial; urgency=medium
* Merge with Debian to fix FTBFS.
systemd (228-3) UNRELEASED; urgency=medium
* debian/rules: Remove temporary debug output from test failures again. All
Debian buildd k
No, I'm running what is in Ubuntu 15.10 (not too different from 15.04),
and we don't have that patch yet. Anyway, if that helps (you can easily
apply it locally), that clarifies this matter for sure. :-) Thanks for
digging out the link!
** Changed in: systemd (Ubuntu)
Status: Incomplete =>
So you run a newer version?
plus.google.com/112206451048767236518/posts/SYAueyXHeEX
Regards
Erkan
On Tue, Jun 02, 2015 at 10:57:46AM -, Martin Pitt wrote:
> Hm, when I do this it seems to be correct:
>
> $ sudo systemd-nspawn -b -D /tmp/schroot-wily-systemd/
>
> "machinectl status schroot
Hm, when I do this it seems to be correct:
$ sudo systemd-nspawn -b -D /tmp/schroot-wily-systemd/
"machinectl status schroot-wily-systemd" shows
Unit: machine-schroot\x2dwily\x2dsystemd.scope
├─12745 /lib/systemd/systemd
[...]
and systemd-cgls shows
├─
The documentation claims machine.slice is the default.
man systemd-nspawn:
--slice=
Make the container part of the specified slice, instead of the
default machine.slice
The machine.slice although still exists. So It is a doku bug? Is there a
changlog telling it is going to chan
Why is one wrong and the other right? I. e. what's the actual bug that's
caused by this layout?
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubunt
Checked with fedora 22.
It is also wrong fedora 22 (systemd 219)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1455828
Title:
machinctl/systemd-nspawn containers/process
7 matches
Mail list logo
