is it the future?

Lars E. Pettersson lars at homer.se
Sat Sep 13 21:26:46 UTC 2014


On 09/12/14 21:12, Kevin Fenzi wrote:
> On Fri, 12 Sep 2014 21:00:01 +0200
> Anders Wegge Keller <wegge at wegge.dk> wrote:
...
>>> If you started a sysvinit service foobar and wanted to look at it's
>>> output, you had to hope the needed info was also in a log file or
>>> kill the service and restart it in some non standard mode to watch
>>> it's output. With systemd/journald, ALL output is saved and easy to
>>> query.
>>
>>   At the cost of extra memory usage and/or disk I/O. Do you run into
>> that kind of problems often enough, that it warrant that? It's not
>> gain for me.
>
> The amount of memory and i/o is trivial, IMHO.

Trivial? Take a look at my nine month old bug report, that has received 
no response whatsoever form the systemd maintainers, about the 
sluggishness of the journal compared to the good old text based log files.

<https://bugzilla.redhat.com/show_bug.cgi?id=1047719>

Even 'systemctl status some_service' take way too long time due to the 
sluggish journal.

Lars
-- 
Lars E. Pettersson <lars at homer.se>
http://www.sm6rpz.se/


More information about the users mailing list