I have very few information in this /var/log/boot.log file, much less than in the dmesg output.
Main Topics
Browse All TopicsI dont' know if I am getting it right, but I have understood that the dmesg kernel messages are stored in /var/log/messages by the help of syslog, and that syslog was adding a timestamp before each message, is that right?
In that case, why are not all messages of dmesg stored in /var/log/messages and would there be a loglevel we could change so that it woudl log all messages from dmesg?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
The output of dmesg seems to contain only the boot up messages. I had a lot of "TCP: Treason uncloaked!" messages when I typed 'dmesg'. I have deleted them with 'dmesg -c', and yet I would like to know where they have been stored. I thought it was in /var/log/messages, but yet they are not there nor in any suggested file above. Isn't this related to a loglevel configuration?
if you want to write the current kernel buffer, you will need to configure syslog accordingly, this differs strongly between syslogd and syslog-ng:
syslog-ng
------------
you need to specify a filter:
filter f_kernel { level(warn) and facility(kern) and not filter(f_iptables)
or level(err) and not facility(authpriv); };
destination log file:
destination custom_log { file("/var/log/kernel_log"
and finally set logging:
log { source(src); filter(f_kernel); destination(custom_log); };
in syslogd
--------------
kern.* /var/log/kernel_log
here are some links:
http://www.softpanorama.or
http://linux.cudeso.be/lin
Hello, Jozk0.
I am using syslogd. The following line in /etc/syslog.conf is probably what I need:
kern.* /var/log/kernel_log
This seems to log almost everything, so I must wait that the event I am looking for comes out again and see if it is there. But as it seems to log all kernel messages, and that dmesg shows all kernel messages, I think that this is the solution to my problem!
Thanks a lot,
Daniel
Business Accounts
Answer for Membership
by: Jozk0Posted on 2007-10-27 at 03:31:12ID: 20161028
they are stored under:
/var/log/boot.msg
this is on opensuse.