[
http://jira.qos.ch/browse/LBCORE-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12347#action_12347
]
Daniel Potter commented on LBCORE-235:
--------------------------------------
Any update on this issue? Another developer submitted a patch and pull request
for the issue on GitHub a while back (https://github.com/ceki/logback/pull/37).
Are there any plans to fold this into a release?
The fallback method of rename-by-copy is essentially broken for
TimeBasedRollingPolicy until this issue is fixed.
> Logback's TimeBasedRollingPolicy can't rename/move a file across filesystems
> ----------------------------------------------------------------------------
>
> Key: LBCORE-235
> URL: http://jira.qos.ch/browse/LBCORE-235
> Project: logback-core
> Issue Type: Bug
> Components: Rolling
> Affects Versions: 0.9.30
> Environment: AIX 6.1, WebSphere 8.0.0.1
> Reporter: Daniel Potter
> Assignee: Logback dev list
>
> Logback can't roll log files to a different filesystem than the active log
> using TimeBasedRollingPolicy (and RenameUtil.rename()) on AIX and possibly
> other Unix/Linux-based operating systems. Per the Java 6 File.renameTo()
> method JavaDoc, "The rename operation might not be able to move a file from
> one filesystem to another". The JavaDoc for RenameUtil.rename() states that
> it should fall back to renaming by copying, but the code doesn't do that.
> The renameByCopying() method is never called.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.qos.ch/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
logback-dev mailing list
[email protected]
http://mailman.qos.ch/mailman/listinfo/logback-dev
