Documentation/devtools/maemo5/syslog
(devtools template) |
(→Usage) |
||
| Line 34: | Line 34: | ||
</pre> | </pre> | ||
| - | Note that | + | Note that with time syslog can fill the root filesystem completely. When that's done by a root process like syslog, it can become so full that the device fails to boot. Several days or even couple of weeks shouldn't be a problem, but it depends on the device usage. So, '''after you don't anymore need syslog, remove it and <tt>rm /var/log/syslog*</tt>.''' |
| - | that the device fails to boot. | + | |
== Links == | == Links == | ||
Revision as of 15:11, 22 April 2010
 |
This article documents a developer tool. A list of available devtools is available, together with installation instructions. |
Contents |
Description
The syslogd daemon is responsible for providing logging of messages received from programs and facilities on the local host as well as from remote hosts.
The klogd daemon listens to kernel message sources and is responsible for prioritizing and processing operating system messages. The klogd daemon can run as a client of syslogd or optionally as a standalone program.
Packages
source: sysklogd
binary: sysklogd, klogd
To install these, run:
sudo gainroot apt-get install sysklogd
Usage
To start the klogd and syslog daemons:
# start sysklogd
Note that with time syslog can fill the root filesystem completely. When that's done by a root process like syslog, it can become so full that the device fails to boot. Several days or even couple of weeks shouldn't be a problem, but it depends on the device usage. So, after you don't anymore need syslog, remove it and rm /var/log/syslog*.
Links
See Also
-