3 ms·
* Want to recover from a corrupted write? Too bad. You get a brand new log! * Want log input from processes that exited? Nope, information is lost (bug 2913
by stonogo 5y ago
* Want to recover from a corrupted write? Too bad. You get a brand new log!
* Want log input from processes that exited? Nope, information is lost (bug 2913)
* Want to validate the certificate of a remote log recipient? Nope! (bug 4092)
* Want to submit changes to the specification to help fix any of the above problems? What specification? The code is the spec!
I am a huge journald fan, but some of these bugs have been around for years and years. It's frustrating as hell, so I don't blame the syslog diehards.
- dale_glass 5y agoWhat's wrong with the first one? I see the approach as a very reasonable one -- don't touch a thing that's already broken. Leave it alone, and start a new good log. If you've ever used reiserfs you'll know fsck isn't guaranteed to make things better.