[opensuse] The status of /var/log/boot.log
Hello, I recently had a nagging question come up in regards to: "What happened to /var/log/boot.log?". I have two systems, one openSUSE 12.2 (server 1) "ls -l /var/log/boot.log; -rw-r--r-- 1 root root 7486 Oct 10 13:53 /var/log/boot.log" and the other openSUSE 12.2 (server 2) "ls -l /var/log/boot.log; ls: cannot access /var/log/boot.log: No such file or directory". What I could dig up thus far was that *boot.msg* was depreciated and systemd now logs to /var/log/messages. This seems puzzling to me as they are no clear information that I could find why /var/log/boot.log exists on one system (and apparently functioning as expected) and missing on another. I was told that there is no specific setting that needs to be change for /var/log/boot.log to work. Anyone have inclination of what is going here? Regards P.S. Although it's documented here http://doc.opensuse.org/documentation/html/openSUSE/opensuse-startup/bk01apa... that you can rely on /var/log/boot.msg. It seems to me this is misinformation and should state accurately that /var/log/boot.msg is depreciated in openSUSE 12.*. Also, there is a not so well know hidden service klog.service that is supposedly to be a replacement for missing /var/log/boot.msg. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2012-10-28 21:19, General Mail wrote:
Hello,
What I could dig up thus far was that *boot.msg* was depreciated
That would be deprecated. The price has not changed.
and systemd now logs to /var/log/messages.
Yes.
Anyone have inclination of what is going here?
Simple: systemd does not write to boot.msg, whereas systemv does. A design decision, that's all. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iF4EAREIAAYFAlCNlHoACgkQja8UbcUWM1zIMwEAmrwthfOQxatGKpQcSqJV00f4 AJTIvgiXH95FyCM2skkA/Reprziue3u9Y/l/ViuEKjwPHig3PlxZQJfIkjhuEpvJ =zhMo -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/28/2012 4:24 PM, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2012-10-28 21:19, General Mail wrote:
Hello,
What I could dig up thus far was that *boot.msg* was depreciated
That would be deprecated. The price has not changed.
I haven't felt the meaning of the price until now
and systemd now logs to /var/log/messages.
Yes.
Thanks for clearing up the obvious
Anyone have inclination of what is going here?
Simple: systemd does not write to boot.msg, whereas systemv does. A design decision, that's all.
I am not against the design decision (/var/log/message is sufficient for me in some cases). I am trying to figure out what exactly is working on one system so I can replicate it later. I like to mentioned: To be honest, I've never followed the systemd debate and I personally not to worried what any decision openSUSE takes in regards to systemd moving forward. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 28/10/12 17:19, General Mail wrote:
Hello,
I recently had a nagging question come up in regards to: "What happened to /var/log/boot.log?".
It has gone away, all messages if any are/will to be stored in the journal. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/28/2012 4:31 PM, Cristian Rodríguez wrote:
On 28/10/12 17:19, General Mail wrote:
Hello,
I recently had a nagging question come up in regards to: "What happened to /var/log/boot.log?".
It has gone away, all messages if any are/will to be stored in the journal.
Which does not explain why it's working on one system. An answer to this question would be very helpful when I plan to replicate the same system to another box and I am not stumped asking myself why it's working SO WELL on Server 1. I use custom Kernel (remotely), so /var/log/boot.log is very useful to me. Regards -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2012-10-28 16:36 (GMT-0400) General Mail composed:
It has gone away, all messages if any are/will to be stored in the journal.
Which does not explain why it's working on one system. An answer to this question would be very helpful when I plan to replicate the same system to another box and I am not stumped asking myself why it's working SO WELL on Server 1. I use custom Kernel (remotely), so /var/log/boot.log is very useful to me.
Did you install fresh on one and upgrade the other? Is sysvinit-init installed on the one that does have boot.log? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/28/2012 4:57 PM, Felix Miata wrote:
On 2012-10-28 16:36 (GMT-0400) General Mail composed:
It has gone away, all messages if any are/will to be stored in the journal.
Which does not explain why it's working on one system. An answer to this question would be very helpful when I plan to replicate the same system to another box and I am not stumped asking myself why it's working SO WELL on Server 1. I use custom Kernel (remotely), so /var/log/boot.log is very useful to me.
Did you install fresh on one and upgrade the other?
Both systems are fresh install
Is sysvinit-init installed on the one that does have boot.log?
This seems like an obvious solution but I ran rpm -qa sysinit-init on both systems, it's not installed. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* General Mail
This seems like an obvious solution but I ran rpm -qa sysinit-init on both systems, it's not installed.
Maybe obvious, but you likely will no every find it that way as the package for sysvinit is oddly: sysvinit -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/28/2012 5:52 PM, Patrick Shanahan wrote:
* General Mail
[10-28-12 17:05]: This seems like an obvious solution but I ran rpm -qa sysinit-init on both systems, it's not installed.
Maybe obvious, but you likely will no every find it that way as the package for sysvinit is oddly: sysvinit
Server1 doesn't have sysvinit installed as oppose to Server2 which has version sysvinit-2.88+-77.3.1.x86_64 installed. However, both systems have sysvinit-tools-2.88+-77.3.1.x86_64 installed. No luck there. Regards -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2012-10-29 15:05 (GMT-0400) General Mail composed:
Server1 doesn't have sysvinit installed as oppose to Server2 which has version sysvinit-2.88+-77.3.1.x86_64 installed. However, both systems have sysvinit-tools-2.88+-77.3.1.x86_64 installed. No luck there.
The question I asked in http://lists.opensuse.org/opensuse/2012-10/msg00785.html was sysvinit-init, which is the one I have to think holds the answer to your OP. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/29/2012 3:24 PM, Felix Miata wrote:
On 2012-10-29 15:05 (GMT-0400) General Mail composed:
Server1 doesn't have sysvinit installed as oppose to Server2 which has version sysvinit-2.88+-77.3.1.x86_64 installed. However, both systems have sysvinit-tools-2.88+-77.3.1.x86_64 installed. No luck there.
The question I asked in http://lists.opensuse.org/opensuse/2012-10/msg00785.html was sysvinit-init, which is the one I have to think holds the answer to your OP.
Yeah, I did respond, check http://lists.opensuse.org/opensuse/2012-10/msg00786.html. sysvinit-init is not installed on neither. Perhaps it was installed at one time (perhaps still is, I would have to check) as the RPM db was once corrupted. I can also check my zypper.logs. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/28/2012 4:19 PM, General Mail wrote:
Hello,
I recently had a nagging question come up in regards to: "What happened to /var/log/boot.log?". I have two systems, one openSUSE 12.2 (server 1) "ls -l /var/log/boot.log; -rw-r--r-- 1 root root 7486 Oct 10 13:53 /var/log/boot.log" and the other openSUSE 12.2 (server 2) "ls -l /var/log/boot.log; ls: cannot access /var/log/boot.log: No such file or directory". What I could dig up thus far was that *boot.msg* was depreciated and systemd now logs to /var/log/messages. This seems puzzling to me as they are no clear information that I could find why /var/log/boot.log exists on one system (and apparently functioning as expected) and missing on another. I was told that there is no specific setting that needs to be change for /var/log/boot.log to work. Anyone have inclination of what is going here?
Regards
P.S. Although it's documented here http://doc.opensuse.org/documentation/html/openSUSE/opensuse-startup/bk01apa... that you can rely on /var/log/boot.msg. It seems to me this is misinformation and should state accurately that /var/log/boot.msg is depreciated in openSUSE 12.*. Also, there is a not so well know hidden service klog.service that is supposedly to be a replacement for missing /var/log/boot.msg.
I found /etc/sysconfig/boot; ENFORCE_BLOGD="no" I thought this could be it but both systems has it set to no -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (5)
-
Carlos E. R.
-
Cristian Rodríguez
-
Felix Miata
-
General Mail
-
Patrick Shanahan