Just a quick question. I saw some strange messages while my pc was booting and I would like to review them but I can’t seem to find the boot log. I thought there was a boot.log file in /var/log but I don’t see one. Did something change in 12.1 and it doesn’t get recorded anymore, or is it somewhere else?
Thanks.
The logfiles are in /var/log. Most can only be accessed by root. In your case, if you want to see the messages displayed at boot it’ll be “boot.msg”, another one to look at is “messages”. Both in /var/log
There is also a script for that and you can find it here: S.L.A.V.E. - SuSE Logfile Automated Viewer Engine - Version 2.55 - Blogs - openSUSE Forums
Thank You,
I don’t see any boot.(anything). There is a messages file, but it’s not clear what lines are from boot.
Is that it? Do I need to enable the (boot) messages maybe?
Just a dumb question. Is this still the case for systemd?
On 02/27/2012 05:36 AM, ccin1492 wrote:
>
> I don’t see any boot.(anything). There is a messages file, but it’s not
> clear what lines are from boot.
type this line in a terminal, press the “Enter” button and then copy
paste the input and output back to here using the instructions here
http://goo.gl/i3wnr
ls -hal /var/log/b*
–
DD http://tinyurl.com/DD-Caveat
What does DistroWatch write about YOU?: http://tinyurl.com/SUSEonDW
Ok, here’ s the output…
% sudo ls -hal /var/log/b*
root's password:
-rw------- 1 root root 0 Nov 10 08:10 /var/log/btmp
On 02/27/2012 05:56 PM, ccin1492 wrote:
>
> Ok, here’ s the output…
ok…two amazing things:
and, i wonder where you got your install media, and if you self tested
it prior to the install, this way: http://tinyurl.com/3qde66h, if you
did not, please check it before replying and tell us if it passed the
validity test, or not…
amazing thing: i asked you to do “ls -hal /var/log/b*” and you did
“sudo ls -hal /var/log/b*” and i wonder why
i wonder if you have customized logrotate or other logging conf files?
–
DD http://tinyurl.com/DD-Caveat
What does DistroWatch write about YOU?: http://tinyurl.com/SUSEonDW
On 02/27/2012 10:06 AM, hcvv wrote:
> Just a dumb question. Is this still the case for -systemd-?
considering the answer i just got to an ls request, it doesn’t seem such
a ‘dumb’ question!
–
DD
What does DistroWatch write about YOU?: http://tinyurl.com/SUSEonDW
Just checked the DVD and it passed the integrity test.
amazing thing: i asked you to do “ls -hal /var/log/b*” and you did
“sudo ls -hal /var/log/b*” and i wonder whyi wonder if you have customized logrotate or other logging conf files?
I have not customized any of the logging conf files at all. It’s all as it should be of the box. The only reason I did “ls” as root was to make sure I didn’t miss anything: maybe a little to paranoid.
On 02/27/2012 07:06 PM, ccin1492 wrote:
> Just checked the DVD and it passed the integrity test.
so, i am now out of ideas…must be something to do with 12.1 or systemd…
try this, next time you boot press F5 and select “system V” and then
when it comes up look in /var/log and see if you see any boot logs…
and, wait for better help…
–
DD http://tinyurl.com/DD-Caveat
What does DistroWatch write about YOU?: http://tinyurl.com/SUSEonDW
maybe a little to paranoid.
On the contrary, you are not paranoid enough. Paranoid people never do anything as root.
True enough, however it was a harmless “ls” command so I figure I couldn’t get myself in to much trouble. 
try this, next time you boot press F5 and select “system V” and then
when it comes up look in /var/log and see if you see any boot logs…
I’ll try this when I get a chance. thanks.
On 2012-02-27 10:06, hcvv wrote:
>
> Knurpht;2443705 Wrote:
>> The logfiles are in /var/log. Most can only be accessed by root. In your
>> case, if you want to see the messages displayed at boot it’ll be
>> “boot.msg”, another one to look at is “messages”. Both in /var/log
> Just a dumb question. Is this still the case for -systemd-?
systemd uses the messages file. whereas systemv uses boot.msg file.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
On 2012-02-27 18:18, DenverD wrote:
> On 02/27/2012 05:56 PM, ccin1492 wrote:
>>
>> Ok, here’ s the output…
>
> ok…two amazing things:
There is nothing amazing, I already said that systemd does not write the
boot logs and this is no bug but intentional. Instead it writes the entries
in the standard messages log via syslog - which is a nuisance, IMO.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
On 02/27/2012 10:53 PM, Carlos E. R. wrote:
> I already said that systemd does not write the
> boot logs
Carlos, you said that at 21:08 and i was ‘amazed’ at 18:18
i’m pretty fast, but i can not read what you write 3+ hours before you
write it…
i can only read it like 30 minutes before 
–
DD
What does DistroWatch write about YOU?: http://tinyurl.com/SUSEonDW
Your right, it’s a royal pain. Is there a way to change the behavior so that it writes out boot.log per chance?
Thanks.
On 2012-02-27 23:09, DenverD wrote:
> On 02/27/2012 10:53 PM, Carlos E. R. wrote:
>> I already said that systemd does not write the
>> boot logs
>
> Carlos, you said that at 21:08 and i was ‘amazed’ at 18:18
>
> i’m pretty fast, but i can not read what you write 3+ hours before you
> write it…
Sorry. I really posted it at a quarter to four o’clock, but did not go up
till I re-powered up the machine several hours later.
I didn’t notice. O:-)
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
On 2012-02-27 23:56, ccin1492 wrote:
> Your right, it’s a royal pain. Is there a way to change the behavior so
> that it writes out boot.log per chance?
Not to my knowledge. I wrote a bugzilla about this, so I know. They told me
it was an intentional feature, so there is no way to put the log where it
was. They don’t want it there.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)