|The Unix and Internet Fundamentals HOWTO, by Eric Raymond|
|The Linux System Logging Daemon||Search for a title, author or keyword|
The Linux System Logging Daemon
By James Mohr. I am regularly confronted by Windows NT users who are overwhelmed by how much information they can collect and process using the Windows NT Event Viewer. It is so nice, they maintain, that occurrences (events) are sorted by system, system security, and applications, and that entries can be filtered and searched. The problem is, that’s where it stops. With the exception of a few security-related events, what you are able to log (or not log) is not configurable under Windows NT. You get whatever Microsoft has decided is necessary, no more and no less. Windows NT, on the other hand, always logs specific events to a specific file. Additionally, Windows NT differentiates between only three different types of logs. This means you may need to wade through hundreds, if not thousands, of entries looking for the right one. With Linux, you can specify both what should be logged and where to log it. The workhorse of the Linux logging system is the system logging daemon, or syslogd.
|The Linux System Logging Daemon||Disclaimer: this link points to content provided by other sites.|