Bering-uClibc 6.x - User Guide - Basic Configuration - Log Files
| 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.
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 |
