Re: [systemd-devel] [PATCH] python-systemd: add version number

2013-04-29 Thread Zbigniew Jędrzejewski-Szmek
On Tue, Apr 23, 2013 at 08:11:03PM +0100, Steven Hiscocks wrote: > From: Steven Hiscocks > > --- > Hi, > > I thought it would be useful to have a version number in the python systemd > module. Hi, I haven't replied to this before because of one reservation. Namely, right now all systemd modules

Re: [systemd-devel] login problems

2013-04-29 Thread Christian Hesse
Zbigniew Jędrzejewski-Szmek on Tue, 2013/04/30 01:05: > On Tue, Apr 30, 2013 at 12:03:24AM +0200, Christian Hesse wrote: > > Hello everybody, > > > > ok, this looks very tricky... I have no idea what happens and I have no > > way to reproduce this. It just happens from time to time - very seldom.

Re: [systemd-devel] login problems

2013-04-29 Thread Jan Alexander Steffens
On Tue, Apr 30, 2013 at 1:05 AM, Zbigniew Jędrzejewski-Szmek wrote: >> This is an Arch Linux system with Linux 3.8.8-1-ARCH and systemd 202-1. >> Any ideas? > Are you using selinux, runinng in enforcing mode? How soon after boot, > and how soon after selinux policy is loaded, does this happen? Th

Re: [systemd-devel] login problems

2013-04-29 Thread Zbigniew Jędrzejewski-Szmek
On Tue, Apr 30, 2013 at 12:03:24AM +0200, Christian Hesse wrote: > Hello everybody, > > ok, this looks very tricky... I have no idea what happens and I have no way > to reproduce this. It just happens from time to time - very seldom. > > If this happens I am not able to log in from lxdm and getty

[systemd-devel] login problems

2013-04-29 Thread Christian Hesse
Hello everybody, ok, this looks very tricky... I have no idea what happens and I have no way to reproduce this. It just happens from time to time - very seldom. If this happens I am not able to log in from lxdm and getty. The only way back into the system is getting a failed login from getty, it

[systemd-devel] journal file corruption again

2013-04-29 Thread Allin Cottrell
This refers back to http://lists.freedesktop.org/archives/systemd-devel/2013-April/010272.html where I reported journal files containing "Invalid object contents". At the time I was running systemd 200, and Cristian Rodríguez replied that this issue was a "journal corruption thingy, well known

Re: [systemd-devel] [PATCH] nspawn: add -M option to optstring

2013-04-29 Thread Zbigniew Jędrzejewski-Szmek
On Mon, Apr 29, 2013 at 01:12:28PM +0300, Evangelos Foutras wrote: > This was missed in commit 7027ff61a34a12487712b382a061c654acc3a679 and > means that the --machine option would work but not its shorthand, -M. For the sake of mail archives, patch applied by Dave Reisner. Zbyszek

Re: [systemd-devel] [PATCH] nspawn: add -M option to optstring

2013-04-29 Thread Dave Reisner
On Mon, Apr 29, 2013 at 01:12:28PM +0300, Evangelos Foutras wrote: > This was missed in commit 7027ff61a34a12487712b382a061c654acc3a679 and > means that the --machine option would work but not its shorthand, -M. > --- Thanks, applied. > src/nspawn/nspawn.c | 2 +- > 1 file changed, 1 insertion(+

[systemd-devel] [PATCH] nspawn: add -M option to optstring

2013-04-29 Thread Evangelos Foutras
This was missed in commit 7027ff61a34a12487712b382a061c654acc3a679 and means that the --machine option would work but not its shorthand, -M. --- src/nspawn/nspawn.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/nspawn/nspawn.c b/src/nspawn/nspawn.c index 7b41571..a49cbc2