On Tue, 30 Apr 2013 11:38, Ruediger Meier <sweet_f_a@...> wrote:
On Tuesday 30 April 2013, Cristian Rodríguez wrote:
On 04/30/2013 02:46 AM, Stefan Seyfried wrote: [snip]
* 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)
How can such untested alpha quality stuff make it into a distro?
Done daily by really big companies: Microsoft, Oracle, ... , the smaller companies take that as example. And: OSS and Fedora ARE the playgrounds for the Pro-versions: SLE + RHEL Yes that hurts, but OTOH there's a big cry for the latest features, examples that I'll give you: - Btrfs - without fs-repair tools for a long time, nice, ne? - systemd in OSS 12.1 + 12.2 was half done at best, 12.3 80-90% done - pulse-audio (did it work anywhere without troubles, yet?) No, as diving the cry for the latest-greatest is, it also hinders in debugging the existing problems, as a day has only 24 hours, for everybody. We made our bed, now we have to lay in it. Back to the Subject: +1 for strong recommend of extra syslog service (syslog-ng / rsyslog). +1 no no recommend, and/or suggest of "systemd-logger" in any package +1 for an added warning in "systemd-logger" Description: "Not ready for use, testing only, logs may disappear with no warning." - Yamaban. PS: @Ruediger: did you test? If no, you did not help to find the bugs. Stefan did so, but did not have enough warning to keep another logging service running. And yes, the docu is ambiguous and unclear.