Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • 2
    If you mention syslog-ng, too, you will have written all there is to say on linux-logging. Excellent answer. Commented Feb 27, 2013 at 20:28
  • I learned a lot and have more sources to read. Thanks! Btw. Why would it be bad to use system logging for apache? And which logs should I want to read? Commented Mar 1, 2013 at 18:16
  • @erikb85 1) Mostly because apache generates a lot of output. I have not had to configure apache in a long time, so I can't remember how flexible it is WRT to sending specific things to syslog (but I'd guess very flexible) 2) WRT logs you want to read, have a look at the logic in your /etc/rsyslog.conf. For example: often stuff above a certain priority will go into /var/log/messages, and stuff below that will go into /var/log/notice. I like to also have a log that contains everything, which makes for double and triple overlap, but if you keep them rotated it is no big deal. Commented Mar 2, 2013 at 16:22
  • Just to confirm, rsyslog is not a daemon wrapper around logrotate, right ? Why so ? Commented Nov 20, 2014 at 10:54
  • @Thomas They perform different purposes, although (r)syslog could implement rotation to spare the need for logrotate. However, having them separate means you can use logrotate on things other than syslog files. Commented Nov 20, 2014 at 13:04