Am 04.04.2014 19:12, schrieb Bruno Friedmann:
Well if only I've still rotating rust for system. I've chosen journald exclusively
I really would not do that, I'd always add syslog-ng in addition. I cannot count the number of times the journald crapped itself and I had files that could not be read. Even better: when the broken file was present I could not read any journal anymore. Basically journalctl was going in circles: 2013-12-21 00:00:01 .... 2013-12-21 12:34:45 .... 2013-12-21 19:20:31 .... --- reboot --- 2013-12-21 00:00:01 .... etc. And just with trial and error (removing one file after another) I was finally able to delete 3 weeks of journal logs to at least be able to read the rest. This happened so often that I finally got tired of filing bugs :-) With syslog-ng, i sometimes after a crash get 4K of \000 in the file, but that's it. And I can just skip over it.
cause I know some report of being perhaps slow on rust and all system here are now powered on ssd. (Tired of sector defects & co)
Slowness is one problem, but being unreliable is really a PITA.
for example I've rotated my log this morning and now
How do you do that? How do you determine which of the files are no longer needed? -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org