Upon boot up, I get lots of new lines added to log files in /var/log concerning apparent problems during boot up. The boot sequence does attempt to show the failure or success during each step as it transitions to the final run level, but is there a good manual or procedure on how to fix each transition, so as to cut down on the amount of pesky warning or error messages?
I am a bit concerned that running a system with warning messages is a bit like running a car low on oil. In the past the goal was to have a perfectly running linux system that came up all the way, and yes, I have seen such. This meant knowing how kernel things work, etc, but still, I would think we would want to pay attention to such things as
1127.997470] ALSA usbaudio.c:1274: 2:1:1: cannot get freq at ep 0x1
894.166132] isofs_fill_super: bread failed, dev=sr0, iso_blknum=16, block=16
and others and work to bring them to a minimum.
Thanks for pointing me to some good material. Right now I am working on things piecemeal as I go along, and it will take a lot of time.
I apologize, if I didn’t dump the 10K’s of log files into this message forum, in case someone asks to see the details, but I am just striving to have the system come up clean, and not with a message like:
Warning: Skipped 98 probes
(whatever that means?? did the kernel just mean that it knew that it is supposed to check 98 things but failed? or that 98 things should have gotten checked but didn’t?)
I’m sure there are some log rotation scripts and such in /etc/cron.d. This stuff can all be tweaked to suite your desires. Should you want a little eye candy to accompany your cleanup, there is an app called “bleachbit”. I think it is available from packman.
On 2010-08-11 21:06, randallrathbun wrote:
>
> Upon boot up, I get lots of new lines added to log files in /var/log
> concerning apparent problems during boot up. The boot sequence does
> attempt to show the failure or success during each step as it
> transitions to the final run level, but is there a good manual or
> procedure on how to fix each transition, so as to cut down on the amount
> of pesky warning or error messages?
If you are convinced that you are getting errors, then you will have to attempt “solve” each one,
one by one.
That’s assuming they are really errors. Most are simply logs of what the kernel is doing. It may try
something, which fails, and then takes an alternate route. A failure can simply mean that the
hardware it was trying to use does not exist.
Which means that they are probably normal, and it is useless to try avoid them, and also wrong. The
system has method to clean most logs after some time, automatically.
To learn what each message might mean, use logic, or study the kernel documentation and sources.
There is no document on messages, as far as I know.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” GM (Elessar))