Difference between revisions of "Bering-uClibc 6.x - User Guide - Basic Configuration - Log Files"
m (→Location and contents of main log files) |
m (→Location and contents of main log files) |
||
| Line 24: | Line 24: | ||
* <code class="filename">cron.log</code> - Keeps information of jobs started from cron. | * <code class="filename">cron.log</code> - Keeps information of jobs started from cron. | ||
* <code class="filename">dmesg</code> - It's a copy of the dmesg output from the kernel booting, showing the devices it has found and if it has been able to configure them at all (aside from userland configuration). | * <code class="filename">dmesg</code> - It's a copy of the dmesg output from the kernel booting, showing the devices it has found and if it has been able to configure them at all (aside from userland configuration). | ||
| + | * <code class="filename">daemon.log</code> - The daemon log at /var/log/daemon.log and contains information about running system and application daemons such as hostapd daemon, the dns daemon dnsmasq or the MySQL database daemon mysqld. This can help you trouble-shoot problems with a particular daemon. | ||
| + | * <code class="filename">debug</code> - The debug log provides detailed debug messages from system and applications which log to syslogd at the DEBUG level. | ||
tbc | tbc | ||
Revision as of 16:47, 20 July 2016
| Basic Configuration - Log Files | ||
|---|---|---|
| Prev | Bering-uClibc 6.x - User Guide | Next |
Contents
Log Files
This chapter explains the location and contents of log files generated on a LEAF Bering-uClibc router, the configuration
in syslog-ng, maintenance with logrotate and how to use spacecheck in lrp.conf.
In a space constraint and long running environment like LEAF Bering-uClibc, it will be useful to understand how log files, which tends to grow unlimited, are created and maintained.
Note: Remote logging is not described in this chapter.
Location and contents of main log files
The log files are usually written into /var/log. Some programs writes their log files in subdirectory of /var/log.
Log files present by default are:
-
auth.log- This file keeps login information, e.g. theloginand the ssh serverdropbearwrites into this file. -
cron.log- Keeps information of jobs started from cron. -
dmesg- It's a copy of the dmesg output from the kernel booting, showing the devices it has found and if it has been able to configure them at all (aside from userland configuration). -
daemon.log- The daemon log at /var/log/daemon.log and contains information about running system and application daemons such as hostapd daemon, the dns daemon dnsmasq or the MySQL database daemon mysqld. This can help you trouble-shoot problems with a particular daemon. -
debug- The debug log provides detailed debug messages from system and applications which log to syslogd at the DEBUG level.
tbc
Configuration of syslog-ng
tbd
Log file maintenance
The task of log file maintenance is accomplished by /usr/bin/logrotate.
logrotate is started daily, weekly and monthly from /etc/cron.daily/multicron-d, /etc/cron.weekly/multicron-w and /etc/cron.monthly/multicron-m.
logrotate keeps the configuration files in /etc/logrotate.d, usually named after the application generating the log file (e.g /etc/logrotate.d/ulogd.
logrotate options
tbd
Using Spacecheck in lrp.conf
tbd
| Prev | Up | Next |
