On 2014-06-04 03:23, Felix Miata wrote:
On 2014-06-04 02:15 (GMT+0200) Carlos E. R. composed:
I don't see anything wrong in there. Your plain text logs are there, and there is rotation and separation.
Missing from 13.1:
boot.msg boot.omsg
Ok, but those two were never handled by syslog, so they are not related to this issue. Not exactly. The content of those get written to /var/log/messages, and timestamped, treated like any other message. They are captured into memory while the kernel is booting (nowhere else to go). Previously, they were written to those two files, and now they are dumped into syslog after the daemon is started. Guessing: possibly they are captured by systemd very early (it can, it is PID 1), and when the syslog daemon is started, they go there. No, I do not like this change, but it is not that bad, and it does makes some sense. AND, if you use plymouth, you do get those two files back ;-) (no, I do not use plymouth)
nscd.log (empty in 12.1)
That is not systemd either. Look into "/etc/nscd.conf": # logfile /var/log/nscd.log Log is disabled. It is up to you to reactivate, if you wish :-) (that there was a zero bytes log in 12.1 mayne was a bug)
What does "separation" mean here?
That you can get different log files for different things. There is a messages file for most messages, a "warn" file where the very important ones go, another for mail, for news, for firewall... and there is a configuration to set this all up, and it has not changed since many years. For example, if your syslog daemon is rsyslog, which I think is the default, it is configured in "/etc/rsyslog.conf".
What do you want to setup, persistent systemd style login? You simply create the journal directory. Don't ask me the details, I don't want it.
What is "persistent systemd style login"?
It is a binary database used by systemd to store messages. You query it with "systemd-journalctl". If you create a certain directory, it goes there, and it can grow a lot. Huge. Telcontar:~ # systemd-journalctl --disk-usage Journals take up 392.7M on disk. Telcontar:~ # And that is not the persistent one, I believe. It is configured in "/etc/systemd/journald.conf". See the man page: Storage= Controls where to store journal data. One of "volatile", "persistent", "auto" and "none". If "volatile", journal log data will be stored only in memory, i.e. below the /run/log/journal hierarchy (which is created if needed). If "persistent", data will be stored preferably on disk, i.e. below the /var/log/journal hierarchy (which is created if needed), with a fallback to /run/log/journal (which is created if needed), during early boot and if the disk is not writable. "auto" is similar to "persistent" but the directory /var/log/journal is not created if needed, so that its existence controls where log data goes. "none" turns off all storage, all log data received will be dropped. Forwarding to other targets, such as the console, the kernel log buffer or a syslog daemon will still work however. Defaults to "auto". So, if you create the directory "/var/log/journal/" it will go there. As I don't have it, it goes to "/run/log/journal" instead, which is a tmpfs. Look:
Telcontar:~ # tree -sh /run/log/journal /run/log/journal └── [ 220] 2ce1d54548517a7307c1c2bc38206d00 ├── [3.0M] system.journal ├── [ 50M] system@8c856da519b04c088359b1a549b7343b-00000000000340ab-0004fa6cd7f4162c.journal ├── [ 45M] system@8c856da519b04c088359b1a549b7343b-0000000000041b59-0004fa7f449259e7.journal ├── [ 50M] system@8c856da519b04c088359b1a549b7343b-000000000004e271-0004fa8f34e921bd.journal ├── [ 50M] system@8c856da519b04c088359b1a549b7343b-000000000005bd77-0004faa848ff39f6.journal ├── [ 50M] system@8c856da519b04c088359b1a549b7343b-0000000000068de3-0004fabba6f47cb2.journal ├── [ 50M] system@8c856da519b04c088359b1a549b7343b-000000000007694e-0004facda6dac9cc.journal ├── [ 50M] system@8c856da519b04c088359b1a549b7343b-0000000000084520-0004fae00d17a9dc.journal └── [ 45M] system@8c856da519b04c088359b1a549b7343b-00000000000921dd-0004faf253c300ec.journal
1 directory, 9 files Telcontar:~ #
(quotes added to break thunderbird line wrapping) Telcontar:~ # du -h /run/log/journal 394M /run/log/journal/2ce1d54548517a7307c1c2bc38206d00 394M /run/log/journal which is RAM and swap. How much in swap, I dunno. (see /usr/src/linux-{VERSION}/Documentation/filesystems/tmpfs.txt)
Or text login? Because your 13.1 system clearly has it.
What is text login? How does that list tell you I have it?
He, because I have been using Linux for more that a decade and I recognize what I see? :-) Most of the files in your /var/log/ are plain text files. Some are compressed, and some are binary (and not generated by systemd). Some are generated directly by services or applications.
Change is not always progress, particularly WRT systemd and things that now depend on it that never depended on Sysvinit.
But in this particular instance, logs have not changed. We simply have two log systems available.
The systemd system appears to be ethereal, and they don't match up exactly.
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.
What I'd really like is to find every log however generated appear in /var/log, and all except the .xz files be human useful/viewable/navigable/searchable initiated with the F3 key in MC, which even before wasn't possible with e.g. btmp, faillog, lastlog and wtmp.
And they are there. Look, those .xz files are just rotated and compressed text files, in the traditional way, nothing changed. You can view them with mc (I just checked mine). If you can't, you are missing some package. If you prefer, you can use any other compression format of your choice. It is configurable, and systemd doesn't intervene here. It is the traditional method. The other four files you mention are binary, and not produced by systemd either. And if you wish, systemd log files also go under /var/log/.
BTW, at 70582K, pbl.log management surely must be broken.
I had not noticed that one before, I don't know what it is. But google knows: just ask it "what is pbl.log", and you find an opensuse form post that says it is "the log file of perl-Bootloader". Big? True... Mine has 35 MB, and it started a year ago. Will have to find out if it is appropriate to add it to the rotation. Could report a bug about it. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)