VectorLinux
September 20, 2014, 03:41:12 am *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Visit our home page for VL info. To search the old message board go to http://vectorlinux.com/forum1. The first VL forum is temporarily offline until we can find a host for it. Thanks for your patience.
 
Now powered by KnowledgeDex.
   Home   Help Search Login Register  
Please support VectorLinux!
Pages: [1]
  Print  
Author Topic: Boot.log Incomplete  (Read 1831 times)
Pita
Vectorian
****
Posts: 1310


« on: May 18, 2007, 08:04:57 pm »

VL-5.8-Gold

I have been wondering for some time why my /var/log/boot.log is incomplete. It is cut at :

Initializing network
Setting up localhost ...                                           
Setting up route ...                                                 
Setting up firewall ...                                       
Caching fonts ...               

The console still shows additional entries, in my case even [failure], however, they do not show in the boot.log. And they run fast and are as well erased on the console once that penguin shows-up asking for a login.

Why is that and can it be corrected in order that the entire boot.log can be accessed?         
Logged
newt
Vectorian
****
Posts: 1132



« Reply #1 on: July 14, 2007, 03:34:57 pm »

I'd also like to find a solution to this.  I have the same issue happening during boot (i.e partial logging) and would like to fix this to log the entire boot process.  Also, I read a recent post here about someone trying to view a similar problem that flashed by so quick it couldn't be read, AND was not reflected in the boot.log or dmesg.  I don't see any kind of boot.log sections in my syslog.conf.  Any suggestions are welcome.

my syslog.conf reads as follows:
Code:
# /etc/syslog.conf
# For info about the format of this file, see "man syslog.conf"
# and /usr/doc/sysklogd/README.linux.  Note the '-' prefixing some
# of these entries;  this omits syncing the file after every logging.
# In the event of a crash, some log information might be lost, so
# if this is a concern to you then you might want to remove the '-'.
# Be advised this will cause a performation loss if you're using
# programs that do heavy logging.

# Uncomment this to see kernel messages on the console.
#kern.*                                                 /dev/console

# Log anything 'info' or higher, but lower than 'warn'.
# Exclude authpriv, cron, mail, and news.  These are logged elsewhere.
*.info;*.!warn;\
        authpriv.none;cron.none;mail.none;news.none     -/var/log/messages

# Log anything 'warn' or higher.
# Exclude authpriv, cron, mail, and news.  These are logged elsewhere.
*.warn;\
        authpriv.none;cron.none;mail.none;news.none     -/var/log/syslog

# Debugging information is logged here.
*.=debug                                                -/var/log/debug

# Private authentication message logging:
authpriv.*                                              -/var/log/secure

# Cron related logs:
cron.*                                                  -/var/log/cron

# Mail related logs:
mail.*                                                  -/var/log/maillog

# Emergency level messages go to all users:
*.emerg                                                 *

# This log is for news and uucp errors:
uucp,news.crit                                          -/var/log/spooler

# Uncomment these if you'd like INN to keep logs on everything.
# You won't need this if you don't run INN (the InterNetNews daemon).
#news.=crit                                     -/var/log/news/news.crit
#news.=err                                      -/var/log/news/news.err
#news.notice                                    -/var/log/news/news.notice

Logged
lagagnon
Global Moderator
Vectorian
*****
Posts: 1922



WWW
« Reply #2 on: July 14, 2007, 06:43:03 pm »

Well I am not a Linux guru but the way I understand the boot logging process is that /var/log/boot.log only logs up to the point where the /etc/rc.d/rc.M script finishes. Anything past that script is local configuration based stuff that exists in /etc/rc.d/rc4.d (or whatever boot level you have set your default to - for most folks that would be runlevel 4).  I understand that final loading of daemons is logged to the bottom of /var/log/messages. So you need to look at both those logs to get a complete picture.

"dmesg" only logs the kernel ring buffer - that is the initial hardware recognition processes of the kernel and this occurs before the boot scripts (such as rc.M) run.

Further understanding of the Linux boot process can be had by reading these gems: http://www.ibm.com/developerworks/library/l-linuxboot/index.html http://openskills.info/infobox.php?IDbox=1042 http://www.slackware.org/config/init.php

 
« Last Edit: July 14, 2007, 06:53:36 pm by lagagnon » Logged

"As people become more intelligent they care less for preachers and more for teachers". Robert G. Ingersoll
newt
Vectorian
****
Posts: 1132



« Reply #3 on: July 14, 2007, 11:42:09 pm »

Thank you for your input lagagnon.  You hit the nail on the head (i.e. information was found in 'messages') - and tought me something about the linux boot processes at the same time.  Thanks for providing the links for more detailed reading.

Cheers and Thanks again!!
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!