[Tickets #12109] 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
  Created 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              | Unconfirmed
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


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

Even with Horde_Core-2.4.3, the problem in some PHP installations is
not fixed completely. Although the Addressbook now opens fine from the
Horde portal, there still is an issue with messages that are being
logged incorrectly.

Since the upgrade to Horde_Core-2.4.2, Horde is spamming my syslog
with messages like

Mar 10 21:30:10 mail horde: [imp] Login success for arjen (Horde user
arjen) [192.168.1.126] to {localhost:143 [imap]} [pid 3574 on line 183
of "/srv/www/htdocs/horde/imp/lib/Auth.php"]

The above is from an ActiveSync client by the way and coincides with
PING and SYNC messages in the webserver log.

I configured logging for level WARNING:

    $conf['log']['priority'] = 'WARNING';
    $conf['log']['ident'] = 'horde';
    $conf['log']['name'] = LOG_LOCAL7;
    $conf['log']['type'] = 'syslog';
    $conf['log']['enabled'] = true;

This message is logged with priority 'NOTICE' (I checked that), which
is lower than the 'WARNING' threshold, so these messages should never
have made it to the syslog.

The behaviour is as expected when downgrading to Horde_Core-2.4.1 and  
seems to be limited to the above messages only (other log messages do  
seem to honor the priority).