syslog-ng FAQ - table of contents

• Where can I find syslog-ng related resources?
• How to help syslog-ng developers to diagnose and fix syslog-ng crash problems?
• How syslog-ng can be used in a chroot environment?
• Can I replace syslogd *and* klogd on my Linux box with syslog-ng?
• How can I keep the timestamp of incoming logs in sync?
• How should my program() destination handle incoming logs?
• Can syslog-ng run as a user other than root?
• How much log traffic can syslog-ng handle?
• How can I link libraries statically from /usr?
• How to make sure, that logs do not fill up my disk space?
• Is there a way for syslog-ng and syslogd to co-exist?
• How can I create a catch-all log destination?
• How can two or more filters be combined?
• Can I set the owner or permission of the created files?
• What is needed to write messages to disk the instant they are received?
• Can output from programs started by syslog-ng be captured and logged by syslog-ng?
• How can I input my logs into a database in real time?
• How to create reports on syslog-ng logs?
• Is it normal, that I always see two syslog-ng processes runing?
• Can I use AppArmor with syslog-ng?
• Why are the log files referenced in my syslog-ng.conf file not created?

A special thanks goes to Nathan Campi, who maintained the syslog-ng FAQ for many years. This FAQ is based on his work, but updated to include information about the latest syslog-ng releases.
If you are looking for information specific to 1.X or 2.0 releases, the old FAQ is still available at http://www.campin.net/syslog-ng/faq.html