[Tickets #13112] 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
  Created By         | bastian-bugs.horde.org at t6l.de
  Summary            | syslog uses priority EMERG
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Bug
  State              | Unconfirmed
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


bastian-bugs.horde.org at t6l.de (2014-04-14 08:20) wrote:

Using commit d143ae4842c7a24741a8f08bce57ca5e879957b2

If configured to use syslog, the Horde framework sends log messages  
with priority EMERG in certain cases.
I am pretty sure you don't want to do this. The priority EMERG intends  
to notify about an instable system on OS or kernel level, afaik. Given  
this, the default rsyslog configuration (from debian stable) sends  
EMERG message to all available consoles. That is very anoying to see  
messages like

{{{
HORDE: User is not authorized [pid 25210 on line 1502 of  
"/home/horde/local/src/horde.git/framework/Core/lib/Horde/Registry.php"]
}}}

popping up and destroying your console work.