You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4php-dev@logging.apache.org by "Christian Grobmeier (JIRA)" <ji...@apache.org> on 2009/05/25 18:02:45 UTC
[jira] Created: (LOG4PHP-51) Create SyslogAppender Test
Create SyslogAppender Test
--------------------------
Key: LOG4PHP-51
URL: https://issues.apache.org/jira/browse/LOG4PHP-51
Project: Log4php
Issue Type: Improvement
Components: Tests
Affects Versions: 2.0
Reporter: Christian Grobmeier
Fix For: 2.0
Create Test for SyslogAppender.
Knut Urdalen:
LoggerAppenderSyslog I would say is ok to use directly and check the syslog file? Maybe we can workaround this and pipe syslog messages somewhere else not to mess up the syslog on the machine?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (LOG4PHP-51) Create SyslogAppender Test
Posted by "Christian Grobmeier (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LOG4PHP-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Grobmeier resolved LOG4PHP-51.
----------------------------------------
Resolution: Fixed
Added dry mode and wrote test. The actuall syslog call is avoided and the output goes to a buffered echo instead. This will help finding the biggest issues
> Create SyslogAppender Test
> --------------------------
>
> Key: LOG4PHP-51
> URL: https://issues.apache.org/jira/browse/LOG4PHP-51
> Project: Log4php
> Issue Type: Improvement
> Components: Tests
> Affects Versions: 2.0
> Reporter: Christian Grobmeier
> Fix For: 2.0
>
>
> Create Test for SyslogAppender.
> Knut Urdalen:
> LoggerAppenderSyslog I would say is ok to use directly and check the syslog file? Maybe we can workaround this and pipe syslog messages somewhere else not to mess up the syslog on the machine?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.