[
https://issues.apache.org/jira/browse/LOG4PHP-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13475005#comment-13475005
]
Charles Mack edited comment on LOG4PHP-196 at 10/12/12 2:12 PM:
----------------------------------------------------------------
Ivan,
Let me see if I can setup a few more tests locally including the Trunk log4php
code. If I can get it to replicate, I'll create post a Youtube clip and
instructions. I suspect that you are not able to replicate this because the
file copy is too quick when rolling (because of file size) and the writes are
too short (because of log message size).
I greatly appreciate your help and patience.
was (Author: cfmack):
Ivan,
Let me see if I can setup a few more tests locally including the Trunk log4php
code. If I can get it to replicate, I'll create post a Youtube clip and
instructions. I greatly appreciate your help and patience.
> Appender Rolling File: Seperate PHP processes attempting to roll the same log
> file will truncate the log.
> ---------------------------------------------------------------------------------------------------------
>
> Key: LOG4PHP-196
> URL: https://issues.apache.org/jira/browse/LOG4PHP-196
> Project: Log4php
> Issue Type: Bug
> Components: Code
> Affects Versions: 2.2.1
> Environment: Windows
> Reporter: Kyle Wiering
> Labels: bug, fix, patch
> Fix For: 2.3.0
>
> Attachments: config_roll_windows.xml, fileroller.php, filewriter.php,
> LoggerAppenderRollingFileWindows.php,
> LoggerAppenderRollingFileWindowsTest.php, LoggerAutoloader.php
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Attaching a class extension to LoggerAppenderRollingFile named
> LoggerAppenderRollingFileWindows. This class enacts 'blocking' to keep
> seperate PHP processes from truncating the log file by attempting to roll the
> logs at/near the same exact time. It also uses a 'rename' in a manner that
> is much quicker then a copy for large files.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
