Re: [systemd-devel] [PATCH v4] use systemd.debug on the kernel command line, not "debug"

2014-04-05 Thread David Timothy Strauss
On Sat, Apr 5, 2014 at 4:06 PM, Jason St. John wrote: > "init.debug" would be better than "systemd.debug", in my opinion. It > is shorter (less typing and no possible end-user confusion over > "systemd.debug" vs. "system.debug"), and it is init-agnostic. Other > init systems (OpenRC, Upstart, etc.

Re: [systemd-devel] Masking .network files

2014-04-05 Thread Leonid Isaev
On Sun, 6 Apr 2014 01:12:45 +0200 Tom Gundersen wrote: > So in general "masking" .network files (in the sense applied to unit > files) does not make much sense, and will probably not behave as you > would expect from knowing unit files. We may very well want to change > this in networkd, but need

Re: [systemd-devel] Masking .network files

2014-04-05 Thread Tom Gundersen
On Sat, Apr 5, 2014 at 5:06 PM, Leonid Isaev wrote: > Hi, > > On Sat, 5 Apr 2014 11:26:17 +0200 > Tom Gundersen wrote: > >> On Sat, Apr 5, 2014 at 12:43 AM, Leonid Isaev wrote: >> > I seem to have a strange issue with the way networkd processes its >> > configuration files. The machine i

Re: [systemd-devel] [PATCH v4] use systemd.debug on the kernel command line, not "debug"

2014-04-05 Thread Jason St. John
On Sat, Apr 5, 2014 at 4:16 PM, Greg KH wrote: > On Sat, Apr 05, 2014 at 07:11:47AM +0200, Zbigniew Jędrzejewski-Szmek wrote: >> On Thu, Apr 03, 2014 at 04:08:15PM +0200, Hannes Reinecke wrote: >> > From: Greg KH >> > >> > If the kernel is started with "debug", that's for the kernel to switch >>

Re: [systemd-devel] [PATCH v4] use systemd.debug on the kernel command line, not "debug"

2014-04-05 Thread Tom Gundersen
On Sat, Apr 5, 2014 at 11:44 PM, Zbigniew Jędrzejewski-Szmek wrote: > On Sat, Apr 05, 2014 at 11:32:50PM +0200, Tom Gundersen wrote: >> On Sat, Apr 5, 2014 at 11:22 PM, Zbigniew Jędrzejewski-Szmek >> wrote: >> > On Sat, Apr 05, 2014 at 01:16:12PM -0700, Greg KH wrote: >> >> On Sat, Apr 05, 2014 a

Re: [systemd-devel] [PATCH v4] use systemd.debug on the kernel command line, not "debug"

2014-04-05 Thread Zbigniew Jędrzejewski-Szmek
On Sat, Apr 05, 2014 at 11:32:50PM +0200, Tom Gundersen wrote: > On Sat, Apr 5, 2014 at 11:22 PM, Zbigniew Jędrzejewski-Szmek > wrote: > > On Sat, Apr 05, 2014 at 01:16:12PM -0700, Greg KH wrote: > >> On Sat, Apr 05, 2014 at 07:11:47AM +0200, Zbigniew Jędrzejewski-Szmek > >> wrote: > >> > On Thu,

Re: [systemd-devel] [PATCH v4] use systemd.debug on the kernel command line, not "debug"

2014-04-05 Thread Reindl Harald
Am 05.04.2014 23:22, schrieb Zbigniew Jędrzejewski-Szmek: > The whole issue started with bug #76935: the original reporter was > seemingly unaware of available kernel commandline options, and his > comments fairly quickly degenerated to rude personal attacks. It's > something that one sees quite o

Re: [systemd-devel] [PATCH v4] use systemd.debug on the kernel command line, not "debug"

2014-04-05 Thread Tom Gundersen
On Sat, Apr 5, 2014 at 11:22 PM, Zbigniew Jędrzejewski-Szmek wrote: > On Sat, Apr 05, 2014 at 01:16:12PM -0700, Greg KH wrote: >> On Sat, Apr 05, 2014 at 07:11:47AM +0200, Zbigniew Jędrzejewski-Szmek wrote: >> > On Thu, Apr 03, 2014 at 04:08:15PM +0200, Hannes Reinecke wrote: >> > > From: Greg KH

Re: [systemd-devel] [PATCH v4] use systemd.debug on the kernel command line, not "debug"

2014-04-05 Thread Zbigniew Jędrzejewski-Szmek
On Sat, Apr 05, 2014 at 01:16:12PM -0700, Greg KH wrote: > On Sat, Apr 05, 2014 at 07:11:47AM +0200, Zbigniew Jędrzejewski-Szmek wrote: > > On Thu, Apr 03, 2014 at 04:08:15PM +0200, Hannes Reinecke wrote: > > > From: Greg KH > > > > > > If the kernel is started with "debug", that's for the kernel

Re: [systemd-devel] LXC not working with systemd 209 or later

2014-04-05 Thread John Lane
On 04/04/14 13:10, Tom Gundersen wrote: On Thu, Apr 3, 2014 at 7:53 PM, John Lane wrote: What I find is that the login prompt never results in a prompt. I enter the correct user/password and it takes an age before redisplaying the login prompt. If apply 208 before starting the container then it

Re: [systemd-devel] LXC not working with systemd 209 or later

2014-04-05 Thread John Lane
On 04/04/14 23:17, Leonid Isaev wrote: On Fri, 04 Apr 2014 21:19:45 +0100 John Lane wrote: [...] I did this: systemd-nspawn -bD /srv/lxc/testcontainer Starting the container this way is pretty-much instantaneous. You can log in and halt it cleanly. Now that's interesting... 3. How do you

Re: [systemd-devel] [PATCH v4] use systemd.debug on the kernel command line, not "debug"

2014-04-05 Thread Greg KH
On Sat, Apr 05, 2014 at 07:11:47AM +0200, Zbigniew Jędrzejewski-Szmek wrote: > On Thu, Apr 03, 2014 at 04:08:15PM +0200, Hannes Reinecke wrote: > > From: Greg KH > > > > If the kernel is started with "debug", that's for the kernel to switch > > into debug mode. We should rely on a namespace for

Re: [systemd-devel] [PATCH] journal-remote-parse: avoid passing null to memchr

2014-04-05 Thread Zbigniew Jędrzejewski-Szmek
On Sat, Apr 05, 2014 at 09:09:47PM +0200, Thomas H.P. Andersen wrote: > static int get_line(RemoteSource *source, char **line, size_t *size) { > ssize_t n, remain; > -char *c; > +char *c = NULL; > char *newbuf = NULL; > size_t newsize = 0; > > @@ -49,7

[systemd-devel] [PATCH] cryptsetup: copy value, not key for (rd.)luks.key

2014-04-05 Thread Matthew Monaco
From: Matthew Monaco --- Really? No one has used this? src/cryptsetup/cryptsetup-generator.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/cryptsetup/cryptsetup-generator.c b/src/cryptsetup/cryptsetup-generator.c index 75d56dd..f4eeb2a 100644 --- a/src/cryptsetup/cry

[systemd-devel] [PATCH] journal-remote-parse: avoid passing null to memchr

2014-04-05 Thread Thomas H.P. Andersen
From: Thomas Hindoe Paaboel Andersen Found with scan-build --- src/journal/journal-remote-parse.c | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/src/journal/journal-remote-parse.c b/src/journal/journal-remote-parse.c index 142de0e..239ff38 100644 --- a/src/journal/jou

Re: [systemd-devel] systemd-git Build failed

2014-04-05 Thread Zbigniew Jędrzejewski-Szmek
On Sat, Apr 05, 2014 at 02:00:33PM +0200, arnaud gaboury wrote: > I am running Archlinux with a custom 3.18.1 Kernel. Full system is upgraded. > > Usually systemd-git build fine using the AUR package[1]. The last two > builds(first one was with linux 3.17) with these errors: > >

Re: [systemd-devel] [PATCH] core: Make sure a stamp file exists for all Persistent=true timers

2014-04-05 Thread Thomas Bächler
Am 05.04.2014 11:35, schrieb Tom Gundersen: > On Wed, Apr 2, 2014 at 8:18 PM, Thomas Bächler wrote: >> If a persistent timer has no stamp file yet, it behaves just like a normal >> timer until it runs for the first time. If the system is always shut down >> while the timer is supposed to run, a st

Re: [systemd-devel] [PATCH] core: Make sure a stamp file exists for all Persistent=true timers

2014-04-05 Thread Zbigniew Jędrzejewski-Szmek
On Sat, Apr 05, 2014 at 11:35:24AM +0200, Tom Gundersen wrote: > On Wed, Apr 2, 2014 at 8:18 PM, Thomas Bächler wrote: > > If a persistent timer has no stamp file yet, it behaves just like a normal > > timer until it runs for the first time. If the system is always shut down > > while the timer is

Re: [systemd-devel] Masking .network files

2014-04-05 Thread Leonid Isaev
Hi, On Sat, 5 Apr 2014 11:26:17 +0200 Tom Gundersen wrote: > On Sat, Apr 5, 2014 at 12:43 AM, Leonid Isaev wrote: > > I seem to have a strange issue with the way networkd processes its > > configuration files. The machine is actually a systemd-nspawn container > > with a static IP addre

[systemd-devel] [PATCH] logind: export *IgnoreInhibited settings to DBus

2014-04-05 Thread Mantas Mikulėnas
--- src/login/logind-dbus.c | 4 1 file changed, 4 insertions(+) diff --git a/src/login/logind-dbus.c b/src/login/logind-dbus.c index 0af6714..0e58955 100644 --- a/src/login/logind-dbus.c +++ b/src/login/logind-dbus.c @@ -1922,6 +1922,10 @@ const sd_bus_vtable manager_vtable[] = { S

Re: [systemd-devel] systemd-git Build failed

2014-04-05 Thread Armin K.
On 04/05/2014 02:00 PM, arnaud gaboury wrote: > I am running Archlinux with a custom 3.18.1 Kernel. Full system is upgraded. > Are you from the future? I doubt that networkd supports kernels from the future :| > Usually systemd-git build fine using the AUR package[1]. The last two > builds(first

[systemd-devel] systemd-git Build failed

2014-04-05 Thread arnaud gaboury
I am running Archlinux with a custom 3.18.1 Kernel. Full system is upgraded. Usually systemd-git build fine using the AUR package[1]. The last two builds(first one was with linux 3.17) with these errors: *** src/libsystemd/sd-rtnl/rtnl-types.c:72:52: error: 'IFLA_BOND_MAX' undec

Re: [systemd-devel] Masking .network files

2014-04-05 Thread Tom Gundersen
On Sat, Apr 5, 2014 at 11:39 AM, Samuli Suominen wrote: > On 05/04/14 12:26, Tom Gundersen wrote: >> matching file will be applied. The 'masking' logic that you know from >> unit files does not really make much sense for .network files (but >> maybe this is something we should change...). Symlinks

Re: [systemd-devel] Masking .network files

2014-04-05 Thread Samuli Suominen
On 05/04/14 12:26, Tom Gundersen wrote: > matching file will be applied. The 'masking' logic that you know from > unit files does not really make much sense for .network files (but > maybe this is something we should change...). Symlinks to /dev/null > are just treated as empty .network files, so t

Re: [systemd-devel] [PATCH] core: Make sure a stamp file exists for all Persistent=true timers

2014-04-05 Thread Tom Gundersen
On Wed, Apr 2, 2014 at 8:18 PM, Thomas Bächler wrote: > If a persistent timer has no stamp file yet, it behaves just like a normal > timer until it runs for the first time. If the system is always shut down > while the timer is supposed to run, a stamp file is never created and > Peristent=true ha

Re: [systemd-devel] Masking .network files

2014-04-05 Thread Tom Gundersen
On Sat, Apr 5, 2014 at 12:43 AM, Leonid Isaev wrote: > I seem to have a strange issue with the way networkd processes its > configuration files. The machine is actually a systemd-nspawn container with > a static IP address, so I had to mask the default 80-container-host0.network > and crea