On 2014-06-04 21:53, Felix Miata wrote:
On 2014-06-04 04:22 (GMT+0200) Carlos E. R. composed:
Each instance of sentence ending in "?" is a question. Your response addressed the second of two questions. What is the answer to the first question? IOW, what is a "text login", and what does it have to do with systemd logging?
Text login refers to the act of having the system create and maintain plain text logs. It is the traditional method. It is what the people opposing systemd want.
and some are binary
Also as I wrote, and one of my complaints. How can the non-.xz files be of any use (why do they clutter /var/log/, and why do they even exist?
Well, man, you should know the answer to that yourself, as they have been that way for a decade. It is the traditional method, and systemd is not involved at all with them. Look, those .xz files are just the compressed old logs. See they have a date in the filename? That's the date when the rotate process took them out and compressed them. It is the traditional method, it has been that way for a decade or two. The only thing that has changed is the choice of compressing methods, because xz compress more than gzip. And you can configure what compression method to use and when and how. As always. And again, systemd is not involved at all in this process, not even in the choice of compression method. If you don't want them compressed, just configure it. No change there, just read the man pages.
Well, but you can use them, or not. Your choice, so far. They are ethereal, if I get your meaning, because openSUSE devs thought better to leave them so, but you can switch them to persistent, if you wish. Some do. I don't.
I don't think you got my meaning. By writing "ethereal" I was referring to the need for journalctl to examine a binary systemd log that does not make any obvious appearance in /var/log/, and cannot be examined via the F3 key on its file highlighted. Anyway this is moot now that I've been instructed that logs in /var/log/ amount to duplications of what's in the ethereal binary blob.
Systemd needs those binary logs for itself, and they are out of the way, so that you do not try to use 'mc' F3 on them, or grep, or whatever. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)