[systemd-devel] [PATCH] util.c: ignore pollfd.revent for loop_read/loop_write

Let read()/write() report any error/EOF. --- src/shared/util.c | 12 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/src/shared/util.c b/src/shared/util.c index 2009553..3c08650 100644 --- a/src/shared/util.c +++ b/src/shared/util.c @@ -2186,8 +2186,10 @@ ssize_t loop_re

[systemd-devel] [PATCH] Fix obsolete references to systemd-random-seed-load.service

This service was merged with systemd-random-seed-save.service in c35b956d34bbb8bb208e49e45de2c103ca11911c. --- src/cryptsetup/cryptsetup-generator.c | 2 +- units/systemd-random-seed.service.in | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/cryptsetup/cryptsetup-genera

[systemd-devel] After poweroff nspawn container can not be started again (with 207)

Hello This works fine with systemd-204. (Running on Linux-3.8.11) # cat /etc/systemd/system/systemd-nspawn@.socket [Unit] Description=The SSH socket of ARCH container in port %I [Socket] ListenStream=%I starting first time: systemd[1]: Starting Container 2... systemd-nspawn[272]: Spawning

Re: [systemd-devel] After poweroff nspawn container can not be started again (with 207)

Looks like your problem similar to https://bugs.freedesktop.org/show_bug.cgi?id=68370 On Sun, Sep 22, 2013 at 10:24 PM, Gerardo Exequiel Pozzi < vmlinuz...@yahoo.com.ar> wrote: > Hello > > This works fine with systemd-204. > (Running on Linux-3.8.11) > > # cat /etc/systemd/system/systemd-nspawn@

Re: [systemd-devel] After poweroff nspawn container can not be started again (with 207)

On 09/22/2013 05:15 PM, Maksim Melnikau wrote: > Looks like your problem similar > to https://bugs.freedesktop.org/show_bug.cgi?id=68370 Thanks. Seems to be the same issue. > > > On Sun, Sep 22, 2013 at 10:24 PM, Gerardo Exequiel Pozzi > mailto:vmlinuz...@yahoo.com.ar>> wrote: > > Hello >

Re: [systemd-devel] libsystemd-bus and libdbus

On Fri, Sep 20, 2013 at 3:48 AM, Karoline Haus wrote: > I'm very interested in systemd's DBUS client library. As far as I understand > it brings significant performance improvements over the standard libdbus > library. > It has actually been designed to one day talk to the kernel-based DBUS > impl

Re: [systemd-devel] Question: who should set up the cpuset cgroup

On 09/18/2013 12:56 AM, Lennart Poettering wrote: > On Tue, 17.09.13 17:45, Lennart Poettering (lenn...@poettering.net) wrote: > >>> 1, set up when systemd creates cpuset cgroup for machine.slice? >>> 2, the programs which create the machines? >>> 3, other ideas? kernel? >> >> I have the suspicion

[systemd-devel] [PATCH v2 2/4] cgroup: show MemoryHierarchy in cgroup_context_dump

Show MemoryHierarchy in cgroup_context_dump. --- src/core/cgroup.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/core/cgroup.c b/src/core/cgroup.c index 68615c3..362b074 100644 --- a/src/core/cgroup.c +++ b/src/core/cgroup.c @@ -92,6 +92,7 @@ void cgroup_context_dump(CGroupContext *c,

[systemd-devel] [PATCH v2 1/4] cgroup: add the setting memory.use_hierarchy support for systemd

Some programs need to set the memory.use_hierarchy(such as libvirt), Add this feature. --- src/core/cgroup.c | 6 ++ src/core/cgroup.h | 1 + src/core/dbus-cgroup.c| 16 src/core/load-fragment-gperf.gperf.m4 | 1 + 4 f

[systemd-devel] [PATCH v2 3/4] systemctl: support setting MemoryHierarchy through systemctl

support setting MemoryHierarchy of unit through systemctl. --- src/systemctl/systemctl.c | 1 + 1 file changed, 1 insertion(+) diff --git a/src/systemctl/systemctl.c b/src/systemctl/systemctl.c index 8b9183d..7d251a0 100644 --- a/src/systemctl/systemctl.c +++ b/src/systemctl/systemctl.c @@ -3644,

[systemd-devel] [PATCH v2 4/4] man: add manpage for MemoryHierarchy

--- man/systemd.cgroup.xml | 11 +++ 1 file changed, 11 insertions(+) diff --git a/man/systemd.cgroup.xml b/man/systemd.cgroup.xml index ac58962..f347f1b 100644 --- a/man/systemd.cgroup.xml +++ b/man/systemd.cgroup.xml @@ -135,6 +135,17 @@ along with systemd; If not, see