On Fri, 27.09.13 09:47, Colin Guthrie (gm...@colin.guthr.ie) wrote:
>
> 'Twas brillig, and Lennart Poettering at 26/09/13 19:35 did gyre and gimble:
> > On Thu, 26.09.13 15:46, Olav Vitters (o...@vitters.nl) wrote:
> >
> >>
> >> On Wed, Sep 11, 2013 at 08:35:49PM +0200, Lennart Poettering wrote:
'Twas brillig, and Lennart Poettering at 26/09/13 19:35 did gyre and gimble:
> On Thu, 26.09.13 15:46, Olav Vitters (o...@vitters.nl) wrote:
>
>>
>> On Wed, Sep 11, 2013 at 08:35:49PM +0200, Lennart Poettering wrote:
>>> (Of course, journald should not exit under any such circumstances, but
>>> to
On Thu, 26.09.13 15:46, Olav Vitters (o...@vitters.nl) wrote:
>
> On Wed, Sep 11, 2013 at 08:35:49PM +0200, Lennart Poettering wrote:
> > (Of course, journald should not exit under any such circumstances, but
> > to find that we first need to track down why it does that currently).
>
> Though it
On Thu, Sep 26, 2013 at 2:46 PM, Olav Vitters wrote:
> On Wed, Sep 11, 2013 at 08:35:49PM +0200, Lennart Poettering wrote:
>> (Of course, journald should not exit under any such circumstances, but
>> to find that we first need to track down why it does that currently).
>
> Though it might hide pro
On Wed, Sep 11, 2013 at 08:35:49PM +0200, Lennart Poettering wrote:
> (Of course, journald should not exit under any such circumstances, but
> to find that we first need to track down why it does that currently).
Though it might hide problems, shouldn't journald be configured to
automatically be r
On Sat, 03.08.13 23:14, Pedro Francisco (pedrogfranci...@gmail.com) wrote:
> (question migrated from t...@lists.fedoraproject.org )
>
> On Fedora 19, journald ( systemd-204-9.fc19.i686 ) stops logging. I
> had enabled lots of iwl3945 debugging ( various messages for each
> iwl3945 interaction --
On Sun, Aug 4, 2013 at 2:43 PM, Zbigniew Jędrzejewski-Szmek
wrote:
> On Sun, Aug 04, 2013 at 01:22:21PM +0200, Kay Sievers wrote:
>> On Sun, Aug 4, 2013 at 12:14 AM, Pedro Francisco
>> wrote:
>> > (question migrated from t...@lists.fedoraproject.org )
>> >
>> > On Fedora 19, journald ( systemd-20
How should I see journald status/log?
sudo systemctl status systemd-journald.service ?
P.S.: /var/lib/systemd/coredump is empty.
On Sun, Aug 4, 2013 at 5:15 AM, Zbigniew Jędrzejewski-Szmek
wrote:
> On Sat, Aug 03, 2013 at 11:14:28PM +0100, Pedro Francisco wrote:
>> (question migrated from t...@
On Sun, Aug 04, 2013 at 01:22:21PM +0200, Kay Sievers wrote:
> On Sun, Aug 4, 2013 at 12:14 AM, Pedro Francisco
> wrote:
> > (question migrated from t...@lists.fedoraproject.org )
> >
> > On Fedora 19, journald ( systemd-204-9.fc19.i686 ) stops logging. I
> > had enabled lots of iwl3945 debugging
On Sun, Aug 4, 2013 at 12:14 AM, Pedro Francisco
wrote:
> (question migrated from t...@lists.fedoraproject.org )
>
> On Fedora 19, journald ( systemd-204-9.fc19.i686 ) stops logging. I
> had enabled lots of iwl3945 debugging ( various messages for each
> iwl3945 interaction -- modprobe iwl3945 deb
On Sat, Aug 03, 2013 at 11:14:28PM +0100, Pedro Francisco wrote:
> (question migrated from t...@lists.fedoraproject.org )
>
> On Fedora 19, journald ( systemd-204-9.fc19.i686 ) stops logging. I
> had enabled lots of iwl3945 debugging ( various messages for each
> iwl3945 interaction -- modprobe iw
(question migrated from t...@lists.fedoraproject.org )
On Fedora 19, journald ( systemd-204-9.fc19.i686 ) stops logging. I
had enabled lots of iwl3945 debugging ( various messages for each
iwl3945 interaction -- modprobe iwl3945 debug=0x47ff ) throughout
the night and the last thing `journalct
12 matches
Mail list logo
