ppkarwasz commented on PR #3872: URL: https://github.com/apache/logging-log4j2/pull/3872#issuecomment-3198120839
@kelunik, Rounding the creation date from the filesystem might address the immediate issue, but I was wondering if it might be more robust to initialize the policy using the file’s **last modification date** instead: * If the rotation interval remains unchanged, the last modification time should still fall within the same rotation period as the creation timestamp, only further away from the interval boundaries. That means the small uncertainties caused by filesystem timestamp caching shouldn’t matter. * The JDK already falls back to the last modification date when it can’t determine the creation date, so this approach is both well-tested and consistent with existing behavior. Would you see any downsides to this alternative? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
