Tickets :: Comment on [#13112] syslog uses priority EMERG

* Your Email Address
* Spam protection	Enter the letters below: .__ ._.. .. ,.__. [ __ \| \| \| \./ \| \| [_./_\|_\|/\\| \| \|__\
Comment	>> The priority EMERG >> intends to notify about an instable system on OS or kernel level, >> afaik. > > You are confusing various logging sub-systems. In the Horde > environment, these are EMERG issues, since they indicate events > that should never, ever happen and require immediate action by the > admin. > > For a Horde-specific logging backend (i.e. a horde-specifc log file) > then EMERG is totally appropriate to describe the issue. > > You instead chose a general-purpose system logging backend that > treats an application EMERG the same as a kernel EMERG. If that is > not what you want, you should either configure syslog to log Horde > actions at a different level or, instead, use a different log backend.
Attachment
Watch this ticket