[logback-dev] [JIRA] Commented: (LBCORE-235) Logback's TimeBasedRollingPolicy can't rename/move a file across filesystems

Daniel Potter (JIRA) noreply-jira at qos.ch
Tue Nov 8 17:32:12 CET 2011


    [ http://jira.qos.ch/browse/LBCORE-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12296#action_12296 ] 

Daniel Potter commented on LBCORE-235:
--------------------------------------

Looks like the call to renameByCopying() was removed back on Jan 13th by Ceki as part of "ongoing work on LBCORE-188 and LBCORE-185".

https://github.com/ceki/logback/commit/2f02bd43fd41dca2a6d0592edbae6968d2080b27#logback-core/src/main/java/ch/qos/logback/core/rolling/helper/RenameUtil.java

> 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

        


More information about the logback-dev mailing list