El 01/11/13 15:19, Ruediger Meier escribió:
On Friday 01 November 2013, Cristian Rodríguez wrote:
El 01/11/13 13:02, Ruediger Meier escribió:
The journal disk-usage is currently 1.3G, which is far to much.
Far too much..in what kind of system .. do you have harddisks from the 90's ? in 2011, the average *consumer* hard drive was 590 GB.. increasing size at a rate of 39% per year.
How ignorant and blind are you ...
So you disagree with me..:-)
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.
We have rpmlint complaining about a few KB documentation in non-doc packages (and much more similar warnings). Not even significant when journald is in use. But not allowed to complain about a journal wasting giga bytes?
Big difference, the size of the journal does not affect the size of the installation media, that's what rpmlint cares about.
Even you always try to convince us that that tmpfs (maybe < 4-8GB on average systems) are enough /tmp for everybody.
Not for everybody, but for the average use, it is not the default and has nothing to do with journal either. -- "Judging by their response, the meanest thing you can do to people on the Internet is to give them really good software for free". - Anil Dash -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org