[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         | Jan Schneider <jan at horde.org>
  Summary            | syslog uses priority EMERG
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Bug
  State              | Not A Bug
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Jan Schneider <jan at horde.org> (2014-04-17 10:52) 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.

I strongly disagree. This could happen all the time with perfectly  
correct and common user behavior. Think of people bookmarking IMP  
instead of Horde, or accessing any other Horde resources (tickets,  
repositories, wiki pages) that require authentication. We already  
handle this gracefully by redirecting to the login screen and from  
there back to the originally requested screen. No reason to log at  
EMERG level there.
But then again, I still cannot reproduce this.