[Tickets #12109] Re: Log priority not honored when logging messages to syslog

[noreply at bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/12109
------------------------------------------------------------------------------
  Ticket             | 12109
  Updated By         | arjen+horde at de-korte.org
  Summary            | Log priority not honored when logging messages to
                     | syslog
  Queue              | Horde Base
  Version            | 5.0.4
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


arjen+horde at de-korte.org (2013-03-12 10:19) wrote:

> Does the ticket subject imply that this doesn't happen if you  
> configure a different logging backend?

It also happens when logging to file, but I wasn't 100% certain that  
the same priority mechanism is used for 'file' too. Since I changed  
logging to 'syslog' well before the upgrade to Horde_Core-2.4.2 (or  
higher) I'm not sure if these messages were suppressed then.

I did prepended the $priority to $event in the log function in  
/usr/share/php5/PEAR/Horde.php, which indicated that these messages  
are indeed logged with priority 'NOTICE', which lead me to believe  
this has probably the same rootcause as  
http://bugs.horde.org/ticket/12103. It does look like messages below  
the configured level in $conf['log']['priority'] are suppressed (as  
expected) most of the time. I never see these messages when using IMP,  
only when using ActiveSync, these are logged every time a client  
connects.