Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Want to do something like

dmesg | tail -f

but it doesn't work: I use Mac OSX 10.6.7, by doing that the tail will exit, instead of monitoring the output.

I wonder if there is any way to do it, or any equivalent command. P.S., I don't think a while loop will be a good enough idea.

share|improve this question

migrated from stackoverflow.com May 27 '11 at 3:00

This question came from our site for professional and enthusiast programmers.

    
that works fine on my Ubuntu 10.04LTS box. A workaround would be to tail whatever logfile that syslog is putting kernel messages into. –  Anonymous May 26 '11 at 21:58
3  
On Mac OSX, that file is /var/log/kernel.log –  Anonymous May 26 '11 at 22:01
    
@Marc Sorry I added my machine spec now. @bobDevil That is cool, but seems that the output is different from dmesg. However this one looks nicer –  Ivan Z. G. Xiao May 26 '11 at 22:06
    
@Anonymous 2: Unfortunately, kernel.log does not contain the same output as dmesg. For example, for a damaged drive, file read errors in dmesg specify exactly which file could not be read, while kernel.log unfortunately provides only the less-than-helpful notice: disk0s2: I/O error. –  Ivan Vučica Oct 25 '11 at 17:41
    
Since linux 3.5, you can do dmesg -w. –  Doug Richardson Sep 12 at 16:10

10 Answers 10

up vote 37 down vote accepted

You are probably looking for some combination of messages from various log files. Try:

tail -f /var/log/{messages,kernel,dmesg,syslog}

…to get a pretty good overview of the system. If you want more or less than that, research what log file the messages you want to see are being placed in.

Also look into using multitail to file and color code and filter multiple log files at once.

share|improve this answer
1  
Thanks for the heads-up re: multitail. Looks interesting. In the case of OS X it'll be something like: tail -f /var/log/{system.log,kernel.log}. –  boehj May 27 '11 at 3:21
    
system.log and kernel.log do not contain the exact output of dmesg on OS X. For example, for a damaged drive, file read errors in dmesg specify exactly which file could not be read, while kernel.log unfortunately provides only the less-than-helpful notice: disk0s2: I/O error. –  Ivan Vučica Oct 25 '11 at 17:45
    
For the record, this answer doesn't work on OS X Mavericks (10.9) or Arch Linux. –  Dan Mundy Dec 24 '13 at 15:31
    
@Dan On Arch you probably don't have a syslog daemon installed or its service enabled. I've noticed that isn't part of the base package set even though it's pretty fundamental. OSX is BSD based and has different paths for a lot of things. You'll need to figure out how and where your system handles logging and adjust. My answer is pretty generic and covers most FHS based distros with syslog enabled, but there are also lots of variant implementations. –  Caleb Dec 24 '13 at 15:38
    
I'm running ubuntu 14.04 and the following tells me whether the link is up or down: sudo tail -f /var/log/kern.log –  user1527227 Jun 10 at 0:28

Just make it @#$%ing work

  1. You want to print output of dmesg, constantly, immediately
  2. Dmesg is printing the kernel ring buffer (see man dmesg)
  3. The kernel ring buffer is a special proc file, /proc/kmsg (see man proc)
  4. Read /proc/kmsg directly, ie cat /proc/kmsg.

Now, if you read the friendly proc manual, it'll sternly warn you to let only one user (who must be privileged) read /proc/kmsg at a time. Whatever syslog implementation you have should be doing this, and presumably it works with dmesg. I dunno, I'm out of my league here, just paraphrasing the manual. So while this is the "just make it @#$%ing work" way, consider the next couple methods first.

Man page approved: watch + dmesg

On Arch gnu/linux with systemd init*, dmesg.log isn't written to very often, perhaps not at all? The best way I found to read the kernel log buffer continuously is with watch. Something like this should get you started (adjust for how many lines fit in your terminal):

watch 'dmesg | tail -50'

watch + dmesg + daemon + tail -f

A more convoluted solution might use watch to write dmesg output to file, which you could then tail -f. You'd probably want this running as a daemon. A proper daemon would also gzip and rotate logs. The following bash code is untested, unworking, and only intended to convey an idea. @Brooks Moses's answer has a working version.

watch 'dmesg >> /var/log/dmesg.log | tail -1'

* tangent, cause this is an osx question, but when systemd is around, don't bother with dmesg, use journalctl -xf (maybe w/ -n 100 to also show the previous 100 lines)

share|improve this answer
    
OS X does not have /proc, however the rest of your answer is applicable. watch can be installed from MacPorts: macports.org –  Ivan Vučica Oct 25 '11 at 17:44
    
@Ivan Vučica Ah, good to know. Wonder where OSX represents the kernel ring buffer.. –  djeikyb Oct 27 '11 at 22:49
1  
Looks like it's directly in the kernel memory. Source code for Apple's dmesg implementation: opensource.apple.com/source/system_cmds/system_cmds-230.7/… Quick Googling doesn't mention anything about it being represented in the filesystem :/ –  Ivan Vučica Oct 28 '11 at 9:24

Here's a variant on djeikyb's answer that's actually tested, and fixes a couple of bugs.

watch 'sudo dmesg -c >> /tmp/dmesg.log; tail -n 40 /tmp/dmesg.log'

The important trick is that we're doing dmesg -c, which clears the ring buffer after it prints -- thus, each time through we're only printing what's new since the last time. You'll need to be root to do that, thus the sudo. There's also a bugfix; instead of trying to both dump the output to a file and pipe it to tail (which doesn't work), we're just reading from the newly-written file.

We could do just dmesg > /tmp/dmesg.log and overwrite the whole file each iteration, but that's a lot of I/O and also risks losing the file if the computer crashes in the middle of an overwrite.

You could also do something similar that's more closely like tail -f with a while loop that executes dmesg -c and sleep 1 forever (see Ben Harris's answer). However, since this is actually clearing the kernel message buffer as it's running, you may also want to pipe things into a logfile in case you want them later.

share|improve this answer

For those interested in linux, since kernel kernel 3.5.0:

# dmesg -w

Also on systems with systemd you can:

# journalctl -kf
share|improve this answer
1  
dmesg -w is the absolutely nicest solution. Unfortunately, even Ubuntu 14.04 doesn't seem to be ready for this because the user space tool doesn't support it yet. –  Daniel Alder Aug 25 at 7:19

Did this before seeing this post:

#!/usr/bin/env perl

use strict;
use warnings;

# "tail -f" for dmesg
# Keeps last printed line. Anything sorting "gt" will be newer

$|=1;

my $y = '';

while(1) {
    for my $k (`dmesg`) {
        if ($k gt $y) {
            print $k;
            $y = $k;
        }
    }        
    sleep 1;
}
exit;
share|improve this answer

you might be able to do:

tail -f /var/log/messages
share|improve this answer
2  
On most systems, the dmesg log file is just a static dump of the dmesg buffer after system boot completes. After that, any new kernel messages usually go into another log file and the dmesg file will stay unchanged until reboot. –  Anonymous May 26 '11 at 22:08
2  
I don't know about "most" systems, but none of the GNU Linux systems I admin behave that way. dmesg reports a current set of the latest messages from the kernel, usually specific to the hardware subsystems. –  Caleb May 27 '11 at 7:26

This may work for you

while true;do sudo dmesg -c;done

Keep in mind that the '-c' flag clears the message buffer into stdout. The 'sudo' is unnecessary if you are root. If you feel this is eating too much of your CPU resource, try adding a 'sleep 1' before the loop is done.

share|improve this answer
    
watch might be good there, if you are watching the screen all of the time –  Seth Robertson May 26 '11 at 22:07
2  
Feel free to cite your sources: linuxforums.org/forum/applications/… –  Anonymous May 26 '11 at 22:08
    
Quick and dirty. Dirty because it only works if you are the only one user doing this. Otherwise each user gets only half of the messages –  Daniel Alder Aug 25 at 7:14

while dmesg -c >> /tmp/dmesg.log; do sleep 0.1; done & tail -f /tmp/dmesg.log

share|improve this answer
    
Please can you explain why this is a solution. –  ChrisF Mar 5 '13 at 12:30
    
It's what some distributions do behind the scenes. It polls the kernel ringbuffer and logs it to /tmp/dmesg.log every 0.1 seconds in a background job while it tails that output. Also, it's the only method that will work if you don't have something special running in the background - or if you've killed all background processes and services and you're doing emergency troubleshooting. –  Dagelf Jun 5 '13 at 18:07

Under the current Ubuntu(I am using Ubuntu 12.04),

tail -f /var/log/syslog

can meet the requirement.

share|improve this answer

response to an old question, but someone might find it useful :)

dmesg | tail -f -

pipes the output of dmesg through tail using the - operator as a shortcut to stdout

share|improve this answer
    
This is the code from the question which does not work. –  pabouk Jan 15 at 8:39
    
It doesn't work because dmesg closes output after closing once. tail -f can't change this anymore. –  Daniel Alder Aug 25 at 7:12

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.