On Thu, Dec 05, 2002 at 09:33:03AM -0800, Ben Hartshorne wrote: > On Wed, Dec 04, 2002 at 11:09:53PM +0100, Sebastiaan wrote: > I'd just like to reiterate something said above. > The boot process can be devided into two sections, kernel boot and > service boot. All the kernel messages from the kernel boot go into > /var/log/dmesg (written from the S55bootmisc.sh in rcS.d). > The services start to boot when you see all the > Starting sshd.... [ok]
Uh, RedHat-ism ;-) > lines go across the screen. It's up to each service to log stuff if > they want to; there's no centralized logging service for those. So, if > one of them is bugging out on you, it's hard to find it logged (unless > it's a nice and kind service). > > This boundary is a little fuzzy when it comes to services that load > kernel modules, such as starting network services. Part of that (the > part that has to do with the kernel) gets logged in /var/log/dmesg, but > there might be other parts that don't. This is true, some bits don't seem to get logged anywhere. As I understand it, kernel 2.6 will improve on this... > One technique I have used to be able to read boot messages takes > advantage of the scrollback buffer in the console. Boot to runlevel 3 > (multiuser, no X) by editing /etc/inittab and changing No. This does not work in Debian, since Debian sets up all (normal) runlevels the same. > You can then scroll back to see what went through the boot sequence (to > a point, I don't know what it is...) by holding down Shift and pressing > the PgUp key. > Don't switch virtual consoles, or you will lose your scrollback buffer. Yep, this would be my advice. -rob
msg17842/pgp00000.pgp
Description: PGP signature
