On Tue, Sep 4, 2012 at 5:10 AM, Matthias Clasen
wrote:
> As I said on irc, the user experience I envision in this case is:
>
> - user closes lid
> - polkit dialog is shown (not useful because the lid is closed)
> - we beep a few times to cause the user to open the lid and see the dialog
> - if the
Hi,
Not sure whether to submit a bug report or documentation patch for this.
ExecStart=/usr/bin/foo --arg1="foo bar"
Causes foo to be run with 2 command line args:
1. --arg1="foo
2. bar"
Not what I was hoping for.
Whereas:
ExecStart=/usr/bin/foo "--arg1=foo bar"
does what I want, just 1 c
Dave Reisner on Tue, 2012/09/04 06:03:
> On Tue, Sep 04, 2012 at 09:44:26AM +0200, Christian Hesse wrote:
> > Hello everybody,
> >
> > a daemon flooded my syslog and rsyslog filled my log partition. After that
> > journald complains on startup:
> >
> > systemd-journald[260]: Failed to open
> > /
On Tue, Sep 04, 2012 at 09:44:26AM +0200, Christian Hesse wrote:
> Hello everybody,
>
> a daemon flooded my syslog and rsyslog filled my log partition. After that
> journald complains on startup:
>
> systemd-journald[260]: Failed to open
> /var/log/journal/d1ba4a2d5fc8ab0c4c46f6f74b607fdd/fss: No
So I can confirm with all six of these patches applied, that everything
now works as it should.
My only question remaining is the semantic change to the functions below.
'Twas brillig, and Colin Guthrie at 03/09/12 23:57 did gyre and gimble:
> diff --git a/src/login/sd-login.c b/src/login/sd-logi
Hello everybody,
a daemon flooded my syslog and rsyslog filled my log partition. After that
journald complains on startup:
systemd-journald[260]: Failed to open
/var/log/journal/d1ba4a2d5fc8ab0c4c46f6f74b607fdd/fss: No such file or
directory
How to fix that?
Everything seems to work without prob
