# System Log
-## Viewing the System Log from LuCi
+## Viewing the system log from LuCi
Select the `Status >> System Log` menu entry.
-![alt text](images/librecmc-selecting-system-log.png "Selecting the
- System Log page in LuCi")
+![alt text](images/librecmc-luci-selecting-system-log.png "Selecting
+ the System Log page in LuCi")
-![alt text](images/librecmc-system-log.png "The System Log page in
- LuCi")
+![alt text](images/librecmc-luci-system-log.png "The System Log page
+ in LuCi")
The `System Log` page in LuCi does not have an interface for filtering
output. Therefore, you will likely want to use the shell interface.
-## Viewing the System Log from the shell
+## Viewing the system log from the shell
Once logged in via SSH, use the `logread` command
-```
+```bash
Usage: logread [options]
Options:
-s <path> Path to ubus socket
For example:
-```
-root@libreCMC:~# logread | grep 'kern\.warn'
+```bash
+root@libreCMC:~$ logread | grep 'kern\.warn'
Mon Jan 15 20:22:01 2018 kern.warn kernel: [ 0.000000] No valid device tree found, continuing without
Mon Jan 15 20:22:01 2018 kern.warn kernel: [ 0.000000] Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes.
Mon Jan 15 20:22:01 2018 kern.warn kernel: [ 0.000000] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
One should be able to use `logread -e` instead of `grep`, but it seems
that not all the same regular expressions work for both:
-```
-root@libreCMC:~# logread -e 'kern\.warn' # and other similar variations
+```bash
+root@libreCMC:~$ logread -e 'kern\.warn' # and other similar variations
(no output)
-````
+```
The system log is contained in a limited size, circular buffer in
memory. So, if you have some process writing messages periodically,