Am 01.05.2013 04:30, schrieb Cristian Rodríguez:
El 30/04/13 21:59, Joachim Schrod escribió:
That's the denial I meant. That something is documented in the manual doesn't mean that it ain't a bug, and a show-stopper for putting things in a distribution, even though some folks like to think it is.
There is no bug, what is happening here is that a the feature required to "fsck" the journal files has not been implemented yet.
The fun thing is, that exactly the thing happened that journal critics had foreseen and which were dismissed as "will not happen" by systemd upstream. * binary format with no tool to read or fix it in case of the slightest problem. All the proposed goodness of the journal is totally useless if you cannot read the logs. If I have a few bytes of garbage in a journal file, it is toast. With the default of one file being 256MB in size (my root partition is 20GB), this will amount to > 3 months of logs lost. With traditional logging, a few bytes of garbage in the logfile will be exactly that: a few bytes of garbage. Nobody will care. I can still extract everything. It is the old problem of data protection vs. data security. The data in the journal is well protected. Protected from getting used by me. -- Stefan Seyfried "If your lighter runs out of fluid or flint and stops making fire, and you can't be bothered to figure out about lighter fluid or flint, that is not Zippo's fault." -- bkw -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org