/etc/rc.d/boot.d/S11boot.klog causing boot problems
 

I'm hoping someone can help me. I was having a problem booting my box, it would stop at an error "Creating /var/log/boot.msg" and the only way I could continue with the boot is "Ctrl-C" (thankfully that worked).

I put echo statements in my /etc/rc.d/boot file and tracked the problem down to a file called /etc/rc.d/boot.d/S11boot.klog

I renamed that file to /etc/rc.d/boot.d/.S11boot.klog (therefore hiding it) and now I can boot and no longer get any error messages.

My question is...... What does the S11boot.klog file do and what happens if I don't load it?

So far, everything seems to be working fine, but I can't imagine the machine wanting to load a file that did NOTHING so I have to be missing some sort of functionality now.

Specifics probably help so I'm running an AMD 266/128M SuSE 8.2 But I didn't think it was version (or distribution specific)

Thanks in advance for your help.

The stuff you mentioned starts the kernel logging. This is not noting, rather quiet useful...

I suggest tracking down your problem again and this time try to get the real problem. Is the dir "/var/log/" existent? Is it writeable? Is the file boot.msg writeable? Is your partition mounted as RW? Look at the file "S11boot.klog" to see what it exactly does, and try again, and again, and again..... :-P

Greetz

Thanks raven,

You were right, I didn't track it down far enough (/me clunks his head on a wall). Turns out that S11boot.klog was just a link to /etc/rc.d/boot.klog.

When I tore boot.klog apart, I tracked my problem down to 1 line: /sbin/klogd -s -o -n -f /var/log/boot.msg

I checked /var/log and it's definately writable. boot.msg is there and I can add to it or overwrite it completely.

I looked at the man page for klogd and I didn't see any problems with how it was being called.

Anything else I can check to see what the problem is?

(the really cool part is I'm amazed I was able to track it down as far as I have been so far - linux doesn't seem all that tough, just a bit confusing still...)

Erm yes...

Look at the boot.klogd file again. Is there a command to create the /var/log/ dir? Maybe boot even hangs after that step. I dont really see what the problem might be.

Anyway, you can check wether /proc is mounted before klogd starts.

And of cource, you could send the script, or at least the relevant parts of it.

Maybe i can tell you more then.

G

raven