[Tickets #13112] Re: syslog uses priority EMERG

noreply at bugs.horde.org noreply at bugs.horde.org
Fri Apr 18 15:44:33 UTC 2014


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              | Not A Bug
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2014-04-18 09:44) wrote:

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

I agree.  And none of these are being logged as EMERG.

What *is* being logged as EMERG is anything that causes a fatal error  
screen.  See Horde_ErrorHandler ('EMERG' logging happens after any  
authentication redirection occurs).

(Also, failure to save compiled CSS and JS files in the static  
directory will cause an EMERG log.  But that is also appropriate,  
since Horde web apps will be unusable without that data.)






More information about the bugs mailing list