[systemd-devel] Booting to systemd in a chroot

Hey folks! I'm getting lots of systemd errors like `Failed at step NAMESPACE spawning /usr/lib/rtkit/rtkit-daemon: Invalid argument` and just wondering what I'm doing wrong. For background: I have a linux computer that's running Debian Wheezy. I want to install and dual boot Jessie, but without c

Re: [systemd-devel] systemd-socket-proxyd usage: remote's directly ping-/telnet-able, but via proxy "Network is unreachable"?

Simple fix. As usual, 5 minutes after posting ... With a helpful prod @ #irc to look at what PrivateNetwork does @ http://www.freedesktop.org/software/systemd/man/systemd.exec.html "If true, sets up a new network namespace for the executed processes and configures only the loopback network

[systemd-devel] systemd-socket-proxyd usage: remote's directly ping-/telnet-able, but via proxy "Network is unreachable"?

I'm attempting to use systemd's socket-proxyd to forward a static IP on a VPS, over a VPN to a mailserver at a remote office location, listening at a NAT'd, internal IP. The mailserver listens @ IP = 10.2.2.12. The staticIP at the VPS is IP = 111.222.333.444 The VPS's staticIP is pingable from

Re: [systemd-devel] [PATCH] sd-bus: fix potential UB in bus_socket_auth_verify_client()

Patchset imported to github. Pull request: -- Generated by https://github.com/haraldh/mail2git ___ systemd-devel

[systemd-devel] [PATCH] sd-bus: fix potential UB in bus_socket_auth_verify_client()

When built with GCC undefined behaviour sanitizer the following problem surfaces: src/libsystemd/sd-bus/bus-socket.c:180:11: runtime error: null pointer passed as argument 1, which is declared to never be null Indeed, calling memmem where b->rbuffer == NULL is undefined behaviour. Fix that by re

Re: [systemd-devel] Crash with extra space after Exec prefix

Am 13.05.2015 um 19:11 schrieb Martin Pitt: Lennart Poettering [2015-05-13 17:55 +0200]: On Wed, 13.05.15 17:01, Martin Pitt (martin.p...@ubuntu.com) wrote: So, obviously we need to fix the crash; but I was wondering what the desired behaviour should be? In the sense of "be liberal what you a

Re: [systemd-devel] Shutting down service using systemd-nspawn

On Thu, 07.05.15 06:38, Peter Paule (systemd-de...@fedux.org) wrote: > > I implemented this now: > > > > http://cgit.freedesktop.org/systemd/systemd/commit/?id=c6c8f6e218995852350e5e35c080dec788c42c3f > > Thanks a lot. Sorry, have seen your mail to late - I'm trying out a new > mua (sup) and I'm

Re: [systemd-devel] Dependency on timers.target

On Thu, 07.05.15 11:26, Bas van Dijk (v.dijk@gmail.com) wrote: > Hello, > > I have a systemd timer (sensors-logger.timer) which requires another > service (carbonCache.service) to be active: > > [Unit] > Requires=carbonCache.service > After=carbonCache.service > Description=Log hardw

Re: [systemd-devel] Crash with extra space after Exec prefix

On Wed, 13.05.15 19:11, Martin Pitt (martin.p...@ubuntu.com) wrote: > Lennart Poettering [2015-05-13 17:55 +0200]: > > On Wed, 13.05.15 17:01, Martin Pitt (martin.p...@ubuntu.com) wrote: > > > So, obviously we need to fix the crash; but I was wondering what the > > > desired behaviour should be? I

Re: [systemd-devel] [PATCH] networkd: don't touch global forwarding setting

On Sun, 10.05.15 20:52, Benedikt Morbach (benedikt.morb...@googlemail.com) wrote: > This reverts commit 43c6d5abacaebf813845934ec8d5e5ee3c431854 > (and a small part of 4046d8361c55c80ab8577aea52523b9e6eab0d0c) > > It turns out we don't actually need to set the global ip_forward setting. > The on

Re: [systemd-devel] Crash with extra space after Exec prefix

Lennart Poettering [2015-05-13 17:55 +0200]: > On Wed, 13.05.15 17:01, Martin Pitt (martin.p...@ubuntu.com) wrote: > > So, obviously we need to fix the crash; but I was wondering what the > > desired behaviour should be? In the sense of "be liberal what you > > accept" I think the extra space(s) sh

Re: [systemd-devel] [PATCH] sd-bus: fix memory leak in test-bus-chat

On Wed, May 13, 2015 at 8:01 AM, Daniel Mack wrote: > We should still keep this flush, right? > >> -sd_bus_unref(bus); >> } >> The cleanup function already does : static inline void sd_bus_close_unrefp(sd_bus **bus) { if (*bus) { sd_bus_flush(*bus)

Re: [systemd-devel] [PATCH] core: fix event source annotations

On Wed, 29.04.15 21:29, Mantas Mikulėnas (graw...@gmail.com) wrote: > These looked like a mass-replace gone slightly wrong – two statements > with no { }'s, and no error checking. > --- > src/core/busname.c | 4 +++- > src/core/manager.c | 5 - > src/core/socket.c | 3 ++- > 3 files changed,

Re: [systemd-devel] [PATCH] nspawn: check the pid in SIGCHLD handler before terminating the container

On Sun, 10.05.15 19:29, Alban Crequy (alban.cre...@gmail.com) wrote: > From: Alban Crequy > > When a process starts systemd-nspawn with exec*() without fork(), > systemd-nspawn can be the parent process of children processes unknown > to systemd-nspawn. It can then receive the signal SIGCHLD for

Re: [systemd-devel] [PATCH] nspawn: cloexec extraneous fds

On Mon, 11.05.15 16:41, Alban Crequy (alban.cre...@gmail.com) wrote: > src/nspawn/nspawn.c | 9 - > 1 file changed, 8 insertions(+), 1 deletion(-) > > diff --git a/src/nspawn/nspawn.c b/src/nspawn/nspawn.c > index 71a6239..2e45c3b 100644 > --- a/src/nspawn/nspawn.c > +++ b/src/nspawn/nsp

Re: [systemd-devel] Reduce unit-loading time

On Wed, 13.05.15 17:51, cee1 (fykc...@gmail.com) wrote: > Hi all, > > We're trying systemd to boot up an ARM board, and find systemd uses > more than one second to load units. > > Comparing with the init of Android on the same board, it manages to > boot the system very fast. > > We guess follo

Re: [systemd-devel] [PATCH 1/1] Fix typo

On Tue, 12.05.15 14:45, Peter Lemenkov (lemen...@gmail.com) wrote: > Looks like sizeof(struct Header) is 240 not 224 Ah indeed. I figure I forgot to update that in 189 when I added the two most new fields. > Signed-off-by: Peter Lemenkov We don't use S-o-b in systemd. Stripped this from the co

Re: [systemd-devel] Crash with extra space after Exec prefix

On Wed, 13.05.15 17:01, Martin Pitt (martin.p...@ubuntu.com) wrote: > Hello all, > > I got a report [1] that you can trivially crash systemd (pid1) at boot > by creating a unit with an Exec= line with a modifier and a space: > > $ cat /tmp/foo.service > [Service] > ExecStart=- /bin/echo hello >

Re: [systemd-devel] [PATCH] [PATCH v3] core: Private*/Protect* options with RootDirectory

On Tue, 12.05.15 15:36, Alban Crequy (alban.cre...@gmail.com) wrote: > diff --git a/src/core/execute.c b/src/core/execute.c > index 1a297ba..d4ccac6 100644 > --- a/src/core/execute.c > +++ b/src/core/execute.c > @@ -1277,6 +1277,7 @@ static int exec_child( > uid_t uid = UID_INVALID; >

[systemd-devel] Crash with extra space after Exec prefix

Hello all, I got a report [1] that you can trivially crash systemd (pid1) at boot by creating a unit with an Exec= line with a modifier and a space: $ cat /tmp/foo.service [Service] ExecStart=- /bin/echo hello $ systemd-analyze verify /tmp/foo.service Assertion 'skip < l' failed at ../src/core/l

Re: [systemd-devel] [PATCH] core: fix memory leak in manager_run_generators()

On Mon, 11.05.15 23:30, Cristian Rodríguez (crrodrig...@opensuse.org) wrote: > If systemd is built with GCC address sanitizer or leak sanitizer > the following memory leak ocurs: Thanks! Applied! > > May 12 02:02:46 linux.site systemd[326]: > ===

Re: [systemd-devel] [PATCH] unit: Set KillMode=mixed for services which use sulogin

On Wed, 13.05.15 16:18, Michael Biebl (mbi...@gmail.com) wrote: > 2015-05-13 15:45 GMT+02:00 Lennart Poettering : > > Well, I am pretty sure that in this case, it should be sulogin that > > propagates the shutdown request to the shell it spawned, but we should > > not do it otherwise. > > > > Note

Re: [systemd-devel] [PATCH] unit: Set KillMode=mixed for services which use sulogin

2015-05-13 15:45 GMT+02:00 Lennart Poettering : > Well, I am pretty sure that in this case, it should be sulogin that > propagates the shutdown request to the shell it spawned, but we should > not do it otherwise. > > Note that by default we don't even clean up processes of unprivileged > users on

Re: [systemd-devel] [PATCH v2 2/2] nspawn: skip symlink to a combined cgroup hierarchy if it already exists

On Wed, 13.05.15 15:45, Iago López Galeiras (i...@endocode.com) wrote: > If a symlink to a combined cgroup hierarchy already exists and points to > the right path, skip it. This avoids an error when the cgroups are set > manually before calling nspawn. Thanks! Applied with some minor modification

Re: [systemd-devel] [PATCH] systemctl: introduce -e and -d for start and stop

Patchset imported to github. Pull request: -- Generated by https://github.com/haraldh/mail2git ___ systemd-devel maili

Re: [systemd-devel] [PATCH v2 1/2] nspawn: only mount the cgroup root if it's not already mounted

On Wed, 13.05.15 15:45, Iago López Galeiras (i...@endocode.com) wrote: > This allows the user to set the cgroups manually before calling > nspawn. Applied! Thanks! > --- > src/nspawn/nspawn.c | 23 +++ > 1 file changed, 11 insertions(+), 12 deletions(-) > > diff --git a/src

Re: [systemd-devel] [PATCH v2] Default to /usr/bin/u?mount, configurable, rather than hard-coded /bin/u?mount.

On Wed, 13.05.15 14:43, Dimitri John Ledkov (dimitri.j.led...@intel.com) wrote: Thanks! Applied! > --- > Makefile.am | 2 ++ > configure.ac| 3 +++ > src/core/execute.h | 2 +- > src/core/mount.c| 12 ++-- > src/core/mount.h

Re: [systemd-devel] [PATCH] systemctl: introduce -e and -d for start and stop

On Wed, 13.05.15 16:39, Mantas Mikulėnas (graw...@gmail.com) wrote: > On Wed, May 13, 2015 at 4:36 PM, Lennart Poettering > wrote: > > > On Wed, 13.05.15 15:21, jsyna...@redhat.com (jsyna...@redhat.com) wrote: > > > > > From: Jan Synacek > > > > Hmm, do we really need two options for this? I me

[systemd-devel] [PATCH v2 1/2] nspawn: only mount the cgroup root if it's not already mounted

This allows the user to set the cgroups manually before calling nspawn. --- src/nspawn/nspawn.c | 23 +++ 1 file changed, 11 insertions(+), 12 deletions(-) diff --git a/src/nspawn/nspawn.c b/src/nspawn/nspawn.c index 8c91726..f292c63 100644 --- a/src/nspawn/nspawn.c +++ b/src/

[systemd-devel] [PATCH v2 0/2] Allow setting the cgroup hierarchy manually before calling nspawn

These two commits allow nspawn to play nicely with a cgroup hierarchy manually set beforehand. Iago López Galeiras (2): nspawn: only mount the cgroup root if it's not already mounted nspawn: skip symlink to a combined cgroup hierarchy if it already exists src/nspawn/nspawn.c | 33 +++

Re: [systemd-devel] [PATCH] fstab-generator: add x-systemd.{after, requires-mounts-for}=

On Wed, 13.05.15 14:28, Dimitri John Ledkov (dimitri.j.led...@intel.com) wrote: > On 13 May 2015 at 13:33, Lennart Poettering wrote: > > On Tue, 12.05.15 19:29, Andrei Borzenkov (arvidj...@gmail.com) wrote: > > > >> All examples can be configured using drop-ins. Do we really need yet > >> another

[systemd-devel] [PATCH v2 2/2] nspawn: skip symlink to a combined cgroup hierarchy if it already exists

If a symlink to a combined cgroup hierarchy already exists and points to the right path, skip it. This avoids an error when the cgroups are set manually before calling nspawn. --- src/nspawn/nspawn.c | 10 -- src/shared/util.c | 23 +++ src/shared/util.h | 1 + 3 f

Re: [systemd-devel] [PATCH] unit: Set KillMode=mixed for services which use sulogin

On Wed, 13.05.15 15:32, Michael Biebl (mbi...@gmail.com) wrote: > 2015-05-13 15:19 GMT+02:00 Lennart Poettering : > > sulogin generally does not set up a PAM session, and we indeed should > > allow processes like screen staying around in such a context. Hence > > KillMode=process is actually the r

[systemd-devel] [PATCH v2] Default to /usr/bin/u?mount, configurable, rather than hard-coded /bin/u?mount.

--- Makefile.am | 2 ++ configure.ac| 3 +++ src/core/execute.h | 2 +- src/core/mount.c| 12 ++-- src/core/mount.h| 4 ++-- src/remount-fs/remount-fs.c | 10 +- 6 files changed, 19 insertions(+), 14 deletions(-)

Re: [systemd-devel] [PATCH] systemctl: introduce -e and -d for start and stop

On Wed, May 13, 2015 at 4:36 PM, Lennart Poettering wrote: > On Wed, 13.05.15 15:21, jsyna...@redhat.com (jsyna...@redhat.com) wrote: > > > From: Jan Synacek > > Hmm, do we really need two options for this? I mean, since -e would > only ever be combined with start, and -d only with stop it could

Re: [systemd-devel] [PATCH] systemctl: introduce -e and -d for start and stop

On Wed, 13.05.15 15:21, jsyna...@redhat.com (jsyna...@redhat.com) wrote: > From: Jan Synacek Hmm, do we really need two options for this? I mean, since -e would only ever be combined with start, and -d only with stop it could as well be a single option that works for both? Also, I am tempted to

Re: [systemd-devel] [PATCH] unit: Set KillMode=mixed for services which use sulogin

2015-05-13 15:19 GMT+02:00 Lennart Poettering : > sulogin generally does not set up a PAM session, and we indeed should > allow processes like screen staying around in such a context. Hence > KillMode=process is actually the right choice for all these services, > indeed. Do you really think it mak

Re: [systemd-devel] [PATCH] Default to /usr/bin/u?mount, configurable, rather than hard-coded /bin/u?mount.

On Wed, 13.05.15 14:24, Dimitri John Ledkov (dimitri.j.led...@intel.com) wrote: > On 13 May 2015 at 14:00, Lennart Poettering wrote: > > On Mon, 11.05.15 16:58, Dimitri John Ledkov (dimitri.j.led...@intel.com) > > wrote: > > > > Hmm, all the other AM_PATH_PROG variables do not carry a _BIN suffi

Re: [systemd-devel] [PATCH] fstab-generator: add x-systemd.{after, requires-mounts-for}=

On 13 May 2015 at 13:33, Lennart Poettering wrote: > On Tue, 12.05.15 19:29, Andrei Borzenkov (arvidj...@gmail.com) wrote: > >> All examples can be configured using drop-ins. Do we really need yet >> another syntax now? > > Well, even though units are all-powerful, I still believe that fstab > is

Re: [systemd-devel] [PATCH] Default to /usr/bin/u?mount, configurable, rather than hard-coded /bin/u?mount.

On 13 May 2015 at 14:00, Lennart Poettering wrote: > On Mon, 11.05.15 16:58, Dimitri John Ledkov (dimitri.j.led...@intel.com) > wrote: > > Hmm, all the other AM_PATH_PROG variables do not carry a _BIN suffix, > should these two? I don't think so. > > (In general, I am not too big a fan of abbrevi

[systemd-devel] [PATCH] systemctl: introduce -e and -d for start and stop

From: Jan Synacek --- man/systemctl.xml | 26 ++ src/systemctl/systemctl.c | 40 ++-- 2 files changed, 60 insertions(+), 6 deletions(-) diff --git a/man/systemctl.xml b/man/systemctl.xml index 4dbdfe1..51c19e1 100644 --- a/man/

Re: [systemd-devel] dev-root.device is not active, results in an umount spree

On 13 May 2015 at 13:43, Lennart Poettering wrote: > On Wed, 13.05.15 12:48, Dimitri John Ledkov (dimitri.j.led...@intel.com) > wrote: > >> I am booting without initramfs, using a plan9 filesystem as rootfs in a kvm. >> >> Thus my /proc/cmdline has: >> root=/dev/root rootflags=rw,trans=virtio,ver

Re: [systemd-devel] [PATCH] unit: Set KillMode=mixed for services which use sulogin

On Tue, 12.05.15 14:36, Michael Biebl (mbi...@gmail.com) wrote: > 2015-05-12 0:03 GMT+02:00 Lennart Poettering : > > On Tue, 12.05.15 00:01, Lennart Poettering (lenn...@poettering.net) wrote: > > > >> On Mon, 11.05.15 23:50, Michael Biebl (mbi...@gmail.com) wrote: > >> > >> > 2015-05-08 17:43 GMT+

Re: [systemd-devel] [PATCH] Default to /usr/bin/u?mount, configurable, rather than hard-coded /bin/u?mount.

On Mon, 11.05.15 16:58, Dimitri John Ledkov (dimitri.j.led...@intel.com) wrote: Hmm, all the other AM_PATH_PROG variables do not carry a _BIN suffix, should these two? I don't think so. (In general, I am not too big a fan of abbreviating things unnecessarily, unless this is commonly done elsewher

Re: [systemd-devel] [PATCH 2/2] nspawn: skip symlink to a combined cgroup hierarchy if it already exists

On Wed, 13.05.15 11:15, Iago López Galeiras (i...@endocode.com) wrote: > -if (symlink(combined, target) < 0) > +if (symlink(combined, target) < 0) { > +if (errno == EEXIST) { > +r = readlink

[systemd-devel] journalctl --directory -f rotation issue

Hi, I'm having a problem with the combination of the --directory (or --file) and the --follow option of journalctl: If followed journal files are rotated, journalctl stops showing new content of those files. Non rotated or new created files are handled properly. After a restart of journalctl th

Re: [systemd-devel] dev-root.device is not active, results in an umount spree

On Wed, 13.05.15 12:48, Dimitri John Ledkov (dimitri.j.led...@intel.com) wrote: > I am booting without initramfs, using a plan9 filesystem as rootfs in a kvm. > > Thus my /proc/cmdline has: > root=/dev/root rootflags=rw,trans=virtio,version=9p2000.L rootfstype=9p > > # mount > /dev/root on / typ

Re: [systemd-devel] [PATCH] fstab-generator: add x-systemd.{after, requires-mounts-for}=

On Tue, 12.05.15 19:29, Andrei Borzenkov (arvidj...@gmail.com) wrote: > All examples can be configured using drop-ins. Do we really need yet > another syntax now? Well, even though units are all-powerful, I still believe that fstab is probably where most people will configure their stuff, simply

Re: [systemd-devel] [PATCH] fstab-generator: add x-systemd.{after, requires-mounts-for}=

On Tue, 12.05.15 18:04, Karel Zak (k...@redhat.com) wrote: > Currently we have no way how to specify dependencies between fstab > entries (or another units) in the /etc/fstab. It means that users are > forced to bypass fstab and write .mount units manually. > > Years ago Lennart suggested to add

Re: [systemd-devel] dev-root.device is not active, results in an umount spree

Heya, On 13 May 2015 at 12:53, Martin Pitt wrote: > Hey Dimitri, > > Dimitri John Ledkov [2015-05-13 12:48 +0100]: >> Yet, dev-root.device is dead: >> # systemctl status dev-root.device >> ● dev-root.device >>Loaded: loaded >>Active: inactive (dead) >> >> This is very bad. As a harmless a

Re: [systemd-devel] dev-root.device is not active, results in an umount spree

Hey Dimitri, Dimitri John Ledkov [2015-05-13 12:48 +0100]: > Yet, dev-root.device is dead: > # systemctl status dev-root.device > ● dev-root.device >Loaded: loaded >Active: inactive (dead) > > This is very bad. As a harmless action like following: > > # mount --bind /opt /opt > > Result

[systemd-devel] dev-root.device is not active, results in an umount spree

I am booting without initramfs, using a plan9 filesystem as rootfs in a kvm. Thus my /proc/cmdline has: root=/dev/root rootflags=rw,trans=virtio,version=9p2000.L rootfstype=9p # mount /dev/root on / type 9p (rw,relatime,sync,dirsync,rw,trans=virtio,version=9p2000.L) Yet, dev-root.device is dead:

Re: [systemd-devel] Reduce unit-loading time

Hi, > -Original Message- > From: systemd-devel [mailto:systemd-devel- > boun...@lists.freedesktop.org] On Behalf Of cee1 > Sent: Wednesday, May 13, 2015 11:52 AM > To: systemd Mailing List > Subject: [systemd-devel] Reduce unit-loading time > > Hi all, > > We're trying systemd to boot up

Re: [systemd-devel] [PATCH] sd-bus: fix memory leak in test-bus-chat

On 05/10/2015 03:14 AM, Cristian Rodríguez wrote: > Building with address sanitizer enabled on GCC 5.1.x a memory leak > is reported because we never close the bus, fix it by using > cleanup variable attribute. > --- > src/libsystemd/sd-bus/test-bus-chat.c | 4 +--- > 1 file changed, 1 insertion(+

Re: [systemd-devel] [PATCH 1/2] nspawn: only mount the cgroup root if it's not already mounted

On Wed, 13.05.15 11:15, Iago López Galeiras (i...@endocode.com) wrote: > This allows the user to set the cgroups manually before calling > nspawn. I think it would be better to simply move mounting of /sys/fs/cgroup into the array at the top of mount_all(), which already does this path_is_mount_p

Re: [systemd-devel] systemd device appeared twice with different sysfs path

On Wed, May 13, 2015 at 06:15:24PM +0800, 李炎戌 wrote: > Hello, everyone!I am a newer to here.Recently, I have a problem. > Whenever I boot my gentoo linux, it output the infomation like following: > [ 11.428530] systemd[1]: Device > dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device

[systemd-devel] systemd device appeared twice with different sysfs path

Hello, everyone!I am a newer to here.Recently, I have a problem. Whenever I boot my gentoo linux, it output the infomation like following: [ 11.428530] systemd[1]: Device dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device appeared twice with dif ferent sysfs paths /sys/devices/pc

Re: [systemd-devel] [PATCH 2/2] nspawn: skip symlink to a combined cgroup hierarchy if it already exists

Patchset imported to github. Pull request: -- Generated by https://github.com/haraldh/mail2git ___ systemd-devel mailing

Re: [systemd-devel] [PATCH] man: mention that tools like imjournal will not work with Storage=none

Zbigniew Jędrzejewski-Szmek píše v Út 12. 05. 2015 v 15:29 +: > On Tue, May 12, 2015 at 05:00:20PM +0200, Lukas Nykryn wrote: > > Manpage for journald.conf mentions that syslog will still work if you > > set Storage=none, but this is not true for some specific setups. > > For example rhel7 and

Re: [systemd-devel] [PATCH] fstab-generator: add x-systemd.{after, requires-mounts-for}=

On 13 May 2015 at 10:15, Karel Zak wrote: > On Wed, May 13, 2015 at 06:35:58AM +0300, Andrei Borzenkov wrote: >> В Tue, 12 May 2015 20:37:15 +0200 >> Karel Zak пишет: >> >> > On Tue, May 12, 2015 at 07:29:33PM +0300, Andrei Borzenkov wrote: >> > > В Tue, 12 May 2015 18:04:50 +0200 >> > > Karel Za

[systemd-devel] Reduce unit-loading time

Hi all, We're trying systemd to boot up an ARM board, and find systemd uses more than one second to load units. Comparing with the init of Android on the same board, it manages to boot the system very fast. We guess following factors are involved: 1. systemd has a much bigger footprint than the

[systemd-devel] [PATCH 2/2] nspawn: skip symlink to a combined cgroup hierarchy if it already exists

If a symlink to a combined cgroup hierarchy already exists and points to the right path, skip it. This avoids an error when the cgroups are set manually before calling nspawn. --- src/nspawn/nspawn.c | 14 -- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/src/nspawn/nsp

[systemd-devel] [PATCH 1/2] nspawn: only mount the cgroup root if it's not already mounted

This allows the user to set the cgroups manually before calling nspawn. --- src/nspawn/nspawn.c | 20 ++-- 1 file changed, 18 insertions(+), 2 deletions(-) diff --git a/src/nspawn/nspawn.c b/src/nspawn/nspawn.c index 2f7dd53..c67cab2 100644 --- a/src/nspawn/nspawn.c +++ b/src/nspa

[systemd-devel] [PATCH 0/2] Allow setting the cgroup hierarchy manually before calling nspawn

These two commits allow nspawn to play nicely with a cgroup hierarchy manually set beforehand. Iago López Galeiras (2): nspawn: only mount the cgroup root if it's not already mounted nspawn: skip symlink to a combined cgroup hierarchy if it already exists src/nspawn/nspawn.c | 34 +++

Re: [systemd-devel] [PATCH] fstab-generator: add x-systemd.{after, requires-mounts-for}=

On Wed, May 13, 2015 at 06:35:58AM +0300, Andrei Borzenkov wrote: > В Tue, 12 May 2015 20:37:15 +0200 > Karel Zak пишет: > > > On Tue, May 12, 2015 at 07:29:33PM +0300, Andrei Borzenkov wrote: > > > В Tue, 12 May 2015 18:04:50 +0200 > > > Karel Zak пишет: > > > > > > > Currently we have no way