서버의 시스템 로그를 볼 수 있습니다. 서버를 들어가면 습관적으로 가장 먼저 입력하는 명령어 입니다.
예를 들면 하드에 문제가 있을 경우 여기에 I/O 에러 관련 로그가 출력됩니다.
root@gw64 ~ [0.05 ]> dmesg
...생략
e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
e1000: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
ADDRCONF(NETDEV_UP): eth1: link is not ready
ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
hrtimer: interrupt took 4949791 ns
eth0: no IPv6 routers present
eth1: no IPv6 routers present
기타 옵션입니다.
-c Clear the ring buffer contents after printing.
-r Print the raw message buffer, i.e., don’t strip the log level
prefixes.
-s bufsize
Use a buffer of size bufsize to query the kernel ring buffer.
This is 16392 by default. (The default kernel syslog buffer
size was 4096 at first, 8192 since 1.3.54, 16384 since 2.1.113.)
If you have set the kernel buffer to be larger than the default
then this option can be used to view the entire buffer.
-n level
Set the level at which logging of messages is done to the con-
sole. For example, -n 1 prevents all messages, except panic
messages, from appearing on the console. All levels of messages
are still written to /proc/kmsg, so syslogd(8) can still be used
to control exactly where kernel messages appear. When the -n
option is used, dmesg will not print or clear the kernel ring
buffer.
When both options are used, only the last option on the command
line will have an effect.
