The Grumpy Editor's guide to surviving the systemd debate
The Grumpy Editor's guide to surviving the systemd debate
Posted Nov 18, 2014 14:51 UTC (Tue) by notninjaz (guest, #99725)In reply to: The Grumpy Editor's guide to surviving the systemd debate by mchapman
Parent article: The Grumpy Editor's guide to surviving the systemd debate
Right, I was referencing the statement: "Yes, it's possible some header corruption could mean an entire file is unreadable. I haven't personally seen that, but I can imagine that it's a concern for some people. You can limit the damage by ensuring the files get rotated frequently. There's {System,RunTime}MaxFileSize config options available; perhaps corresponding {System,RunTime}MaxRotateInterval might be useful. Worst comes to worst, you could just SIGUSR2 the journald process regularly from Cron or a timer unit."
I meant to express a design preference rather to critique any particular software with regard to text vs. binary logs.
