Re: [systemd-devel] [PATCH] networkd: do not change kernel forwarding parameters when IPForwarding is unset

On Fri, May 01, 2015 at 02:05:11PM -0700, Nick Owens wrote: > From: Nick Owens > > --- > man/systemd.network.xml| 6 +++--- > src/network/networkd-link.c| 24 > src/network/networkd-network.c | 2 ++ > src/network/networkd.h | 1 + > 4 files change

Re: [systemd-devel] [PATCH] networkd: do not change kernel forwarding parameters when IPForwarding is unset

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

[systemd-devel] [PATCH] networkd: do not change kernel forwarding parameters when IPForwarding is unset

From: Nick Owens --- man/systemd.network.xml| 6 +++--- src/network/networkd-link.c| 24 src/network/networkd-network.c | 2 ++ src/network/networkd.h | 1 + 4 files changed, 18 insertions(+), 15 deletions(-) the following patch should address ht

Re: [systemd-devel] Deadlocks with reloading jobs which are part of current transaction

On Mon, 2015-04-27 at 18:07 +0200, Lennart Poettering wrote: > On Wed, 04.02.15 23:48, Uoti Urpala ([email protected]) wrote: > > If you mean something like "systemctl restart --no-block > > mydaemon-convert-config.service; systemctl reload mydaemon.service", I > > don't see why you'd ever /e

[systemd-devel] systemd-nspawn --template: should it delete /etc/hostname?

Hello! If I create a new machine by cloning using systemd-nspawn --template, should it remove etc/hostname? It already creates a new machine-id etc, and the hostname should probably not be set for a new container in this case, regardless of whether the template is a real template or a cloned ma

[systemd-devel] systemd-nspawn: cannot join existing macvlan

Hello! I'm not sure about this but I suspect that I cannot start a second nspawn container with --network-macvlan when another nspawn instance has created it before: # systemd-nspawn -b --network-macvlan=enp4s0 Spawning container gentoo-mysql-base on /var/lib/machines/gentoo-mysql-base. Press ^

Re: [systemd-devel] [PATCH v3] journalctl: Improve boot ID lookup

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

[systemd-devel] [PATCH v3] journalctl: Improve boot ID lookup

This method should greatly improve offset based lookup, by simply jumping from one boot to the next boot. It starts at the journal head to get the a boot ID, makes a _BOOT_ID match and then comes from the opposite journal direction (tail) to get to the end that boot. After flushing the matches and

Re: [systemd-devel] [PATCH] Add VARIANT as a standard value for /etc/os-release

On Wed, 2015-04-29 at 08:19 -0400, Stephen Gallagher wrote: > Some distributions (such as Fedora) are using the VARIANT field to > indicate to select packages which of several default configurations > they should be using. For example, VARIANT=Server provides a > different default firewall configur

Re: [systemd-devel] pam_systemd.so indirectly calling pam_acct_mgmt

On Fri, 2015-05-01 at 11:46 +0200, Tomasz Torcz wrote: > On Fri, May 01, 2015 at 09:46:26AM +0100, Colin Guthrie wrote: > > Stephen Gallagher wrote on 30/04/15 14:04: > > > On Thu, 2015-04-30 at 15:01 +0200, Lennart Poettering wrote: > > > > On Thu, 30.04.15 08:54, Stephen Gallagher (sgall...@redha

Re: [systemd-devel] udev interface naming for SR-IOV VFs

On Mon, Apr 20, 2015 at 08:43:21PM +0200, Lennart Poettering wrote: > On Fri, 17.04.15 14:19, Nir Soffer ([email protected]) wrote: > > > - You may wait for unrelated events that happen to trigger in the same > > time, waiting after the new interfaces are ready. > > > > I think you need somethin

Re: [systemd-devel] pam_systemd.so indirectly calling pam_acct_mgmt

On Fri, May 01, 2015 at 09:46:26AM +0100, Colin Guthrie wrote: > Stephen Gallagher wrote on 30/04/15 14:04: > > On Thu, 2015-04-30 at 15:01 +0200, Lennart Poettering wrote: > >> On Thu, 30.04.15 08:54, Stephen Gallagher ([email protected]) > >> wrote: > >> > >>> Does set-linger persist across re

[systemd-devel] mount crypto_LUKS device in conatiner

My container will need access to a Luks encrypted device (/dev/sdd4) for its DB. Here is the setup on the host : - # cryptsetup --key-file /etc/keys/poppy.luks luksOpen /dev/bcache0 sdd4_crypt $ lsblk -o NAME,KNAME,MAJ:MIN,FSTYPE,LABEL

Re: [systemd-devel] pam_systemd.so indirectly calling pam_acct_mgmt

Stephen Gallagher wrote on 30/04/15 14:04: > On Thu, 2015-04-30 at 15:01 +0200, Lennart Poettering wrote: >> On Thu, 30.04.15 08:54, Stephen Gallagher ([email protected]) >> wrote: >> >>> Does set-linger persist across reboots? >> >> Yes it does. When a systemd is booted up with a user that has

Re: [systemd-devel] sd-bus vs gdbus on dbus-daemon

On Thu, Apr 30, 2015 at 11:13 AM, Umut Tezduyar Lindskog wrote: > Hi Simon, > > On Wed, Apr 29, 2015 at 5:34 PM, Simon McVittie > wrote: >> On 29/04/15 15:08, Umut Tezduyar Lindskog wrote: >>> We [1] have noticed that there could be up to %50 performance gain on >>> using sd-bus over gdbus on dbu