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/07/26 13:47:15 UTC
[jira] Updated: (LOG4PHP-57) "please shutdown all loggers" - we
have destructors for this!
[ https://issues.apache.org/jira/browse/LOG4PHP-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Grobmeier updated LOG4PHP-57:
---------------------------------------
Fix Version/s: 2.0
> "please shutdown all loggers" - we have destructors for this!
> -------------------------------------------------------------
>
> Key: LOG4PHP-57
> URL: https://issues.apache.org/jira/browse/LOG4PHP-57
> Project: Log4php
> Issue Type: Improvement
> Components: Code
> Affects Versions: 2.2
> Reporter: Christian Hammers
> Fix For: 2.0
>
>
> From the intro:
> "Last but not least, please shutdown all loggers, appenders and whatever with:
> LoggerManager::shutdown();"
> I guess closing open files should be handled in __desctruct().
> (I did not check how e.g. file appenders are implemented but it should be considered to flush them after writing or
> at least offer some kind of "synchronized" mode because if an application crashes, the very last message should not
> be lost just because PHP did not yet run the __destruct()).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.