On Thu, Dec 22, 2016 at 5:39 PM, Carlos E. R.
and syslog says:
2016-12-22T14:01:16.180279+01:00 Minas-Anor rsyslogd: [origin software="rsyslogd" swVersion="8.4.0" x-pid="3986" x-info="http://www.rsyslog.com"] start 2016-12-22T14:01:16.181997+01:00 Minas-Anor systemd[1]: Listening on Syslog Socket. 2016-12-22T14:01:16.182028+01:00 Minas-Anor systemd[1]: Starting System Logging Service... 2016-12-22T14:01:16.182438+01:00 Minas-Anor systemd[1]: Started System Logging Service. 2016-12-22T14:01:16.184725+01:00 Minas-Anor kernel: [ 0.000000] microcode: CPU0 microcode updated early to revision 0xa0b, date = 2010-09-28 2016-12-22T14:01:16.184737+01:00 Minas-Anor kernel: [ 0.000000] Initializing cgroup subsys cpuset 2016-12-22T14:01:16.184739+01:00 Minas-Anor kernel: [ 0.000000] Initializing cgroup subsys cpu 2016-12-22T14:01:16.184741+01:00 Minas-Anor kernel: [ 0.000000] Initializing cgroup subsys cpuacct
So it captured the current boot or close to it.
That's only kernel messages that it likely gets directly from kmsg. Try logger - does it appear in /var/log/messages? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org