On Monday 23 March 2020 15:16:33 Joe wrote: > On Mon, 23 Mar 2020 13:15:13 -0400 > > Greg Wooledge <wool...@eeg.ccf.org> wrote: > > 5) It does not write logs in human-readable files. You need > > systemd's tools to read systemd's logs. This makes post mortem > > diagnostics much more difficult. > > You might add 5a): Why? > > There's not exactly a burning need to compress text into illegibility > to save disc space these days. How many rational purposes are there to > make logs readable only through systemd's own code?
NONE!!!! Thats my Main objection to it. If it can't leave logs in plain "This is what you need to do text", in the users first language with instructions right in the log, one of us needs to get up and leave the party. The current practice of posting the error, and praying someone can make ones native language out of it is the stuff found on the ground behind the male of the bovine specie. That which I have managed to get my head wrapped around, do seem to be a better idea. But thats far from all of it at the present time. For starters, lets say you know you are having a dhcpd problem, so you go read man dhcpd, and it has nothing to say about it if its now managed by systemd. Hells bells, people, at least put a "see also man xxxxxxx" pointing at the systemd managed version of its man page. That along would ease the transition, and reduce the the systemd hate and discontent on ALL of these lists. And justify the reason for the individual change. None of us like being kept in the dark. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
