You are not logged in.
Googling suggests that the following is a safe method to monitor dmesg in a shell. I'd prefer not to use sudo. Any suggestions? Is it safe to chmod 644 /var/log/kernel.log or is that a bad idea?
$ sudo watch /proc/kmsgor
sudo tail -f /var/log/kernel.logLast edited by graysky (2012-07-29 19:03:24)
Offline
The group of most log files is 'log' and group has read access, so you could add yourself to the log group (but I don't know if it's used for other things/if this is a good idea).
Offline
Use the log group, it's perfectly safe.
Offline
The group of most log files is 'log' and group has read access, so you could add yourself to the log group (but I don't know if it's used for other things/if this is a good idea).
Nice, thanks!
Last edited by graysky (2012-07-29 19:03:15)
Offline
With linux 3.5 and util-linux 2.22, you'll be able to dmesg --follow.
Good to know, Dave. Thank you. Just waiting for CK to port ck1 from 3.4 to 3.5 ![]()
Offline