[Tickets #13112] Re: syslog uses priority EMERG

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/13112
------------------------------------------------------------------------------
  Ticket             | 13112
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | syslog uses priority EMERG
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Bug
-State              | Feedback
+State              | Not A Bug
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2014-04-16 14:59) wrote:

> 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.