David Jensen wrote: > Bryan Kadzban wrote: >> Bruce Dubbs wrote: >> >>> To stop klogd from trying to read System.map, it requires passing -x >>> in the command line. We can do that easily in the boot scripts. >>> >> Which I would suggest if we want to silence the warning. Given the >> (total lack of) need for System.map for the past seven years, I think we >> should also expunge any reference to it from the book, but whatever. >> >> > from slackware rc.syslog > # '-c 3' = display level 'error' or higher messages on console
Starting to get off topic now, but after reading the klogd manpage, this is exactly what the current LFS bootscripts do when you set LOGLEVEL in /etc/sysconfig/console, and the /etc/rc.d/init.d/consolelog script runs: dmesg -n $LOGLEVEL So you could accomplish exactly this with the stock bootscripts, just by setting LOGLEVEL=3 there; no change required to the klogd script. (Well, almost "exactly this". Setting the value to 3 doesn't display "level 'error' or higher" on the console. 3 is KERN_ERR, but the kernel displays only messages *worse* than the level you set. So you get "levels higher than 'error'" on the console: KERN_CRIT, KERN_ALERT, and KERN_EMERG. But that's the case with klogd as well; your comment doesn't match the arguments given. :-) )
signature.asc
Description: OpenPGP digital signature
-- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
