Mailinglist Archive: opensuse-factory (1029 mails)

< Previous Next >
Re: [opensuse-factory] Re: journalctl very slow
On Fri, Nov 1, 2013 at 8:17 PM, Cristian Rodríguez
<crrodriguez@xxxxxxxxxxxx> wrote:

IMHO a no-go for any 'real' core OS developer, but, well, look
at who's in charge of that project upstream....

And that's your argument, an ad-homimem attack.. all nicely bundled with a
"not true scotsman fallacy" .,. is that the best you can do ?

Don't be negligently dismissive. He's on target. It's a bad data
structure for disk access, it was a bad idea, and it's just a matter
of the devs getting the necessary years of woes to be able to give up
their egos and accept that.

Nevertheless, my previous mail stands. It's possible to improve it
without much effort, by telling the kernel what to expect.

On Fri, Nov 1, 2013 at 3:53 PM, Cristian Rodríguez
<crrodriguez@xxxxxxxxxxxx> wrote:

Journalctl showing the logs with 2K/s - that's 60's style

In 2013 systemd-journal (the default in most distros :) needs a week to
show such a 1.3G journal ... it can't even handle 90's file sizes but
you complain that users don't always want to keep their / small.

if 1.3G is too big for your usecase, you can configure the maximum size that
the journal can use on disk, or configure it to only retain the logs of the
current boot at a particular limit (embedded developers do this all the time
as they have limited ram, slower media) or set the Journal storage to none,
which is not recommended and then you must have a syslog implementation
installed .you will loose pretty much all systemd functionality that depends
on logging.

I think the amount of metadata should also be configurable, if that's
the main reason for bloat. I suspect it's not the case though.

Also, having the journal, a memory-mapped write-heavy structure, on an
SSD, is a good way to burn it prematurely.

On Sat, Nov 2, 2013 at 12:25 AM, Andrey Borzenkov <arvidjaar@xxxxxxxxx> wrote:
El 01/11/13 13:03, Archie Cobbs escribió:
On Fri, Nov 1, 2013 at 10:38 AM, Yamaban <foerster@xxxxxxxx> wrote:
But, yes, clear upstream trouble, that is: ignored by those in charge,
sounds of '... rotating media are a dying type ...' where made, when
asked on the topic during a Linux conf earlier this year.

Do not hope for a solution from the systemd / journald side, install
a full 'traditional' syslog.

Maybe this should be the openSUSE default.

I for one am very bothered by the way systemd has made logging more
opaque and cumbersome. Logs are like bread and water to sysadmins.

If you install a traditional syslog implementation there will be no

Then it should be default setting in openSUSE until problem with
journald slowness is fixed, should not it?

Yes. I think it is, in fact. Or at least seemed to last time I
installed 13.1 RC1. Will have to double-check.
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-factory+owner@xxxxxxxxxxxx

< Previous Next >