On 04/30/2013 02:46 AM, Stefan Seyfried wrote:
I give a sh*t on that design document, as long as I can not read my logs, it is the end of the month and they would be very useful to do my accounting.
Fun facts about sytemd-journal: * it logs to a binary database
Yes.
* it can not filter out the user session logs from the system logs
Something can be done about that..I thought it was able to so
* if the database is broken, i tells you (journalctl --verify) * but it can not repair or recover it
That's why it is called --verify and not --repair .. (not implemented yet, never advertised as repair either)
* even if the database is not broken, it can not read it (bnc#817778)
Yes, it can be slow, anyway that looks more like a bug.
* fills the disk way beyound its configured limits (bnc#817780)
"the journald states in the logs: "Allowing runtime journal files to grow to 394.8M." but: susi:~ # journalctl --disk-usage Journals take up 501.9M on disk. epic fail :-) " Yes, epic fail of **your understanding** of the message you are seeing. It says "Allowing **runtime** journal files" .. "runtime journal files" are those living in /run not the ones living in /var/log/journal. journalctl --disk-usage accounts for total size of runtime+ system. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org