[
https://issues.apache.org/jira/browse/SLING-1538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger resolved SLING-1538.
--------------------------------------
Resolution: Fixed
Thanks for reporting.
Yes, you are right. The file is of course not copied but renamed and a new file
is created with the old name. I have fixed the site documentation (which takes
some time to get published).
> Check (and if necessary correct) statement about file rotation
> --------------------------------------------------------------
>
> Key: SLING-1538
> URL: https://issues.apache.org/jira/browse/SLING-1538
> Project: Sling
> Issue Type: Improvement
> Components: Documentation
> Reporter: Alison Heimoz
> Assignee: Felix Meschberger
> Priority: Minor
>
> http://sling.apache.org/site/logging.html -> Scheduled Rotation
> States:
> For example, if the log file is configured as /foo/bar.log and the
> pattern set to '.'yyyy-MM-dd, on 2001-02-16 at midnight, the logging file
> /foo/bar.log
> will be copied to /foo/bar.log.2001-02-16 and logging for 2001-02-17
> will continue in /foo/bar.log until it rolls over the next day.
> Taken literally this means that:
> - the content of /foo/bar.log is copied (ie duplicated; original stays in
> /foo/bar.log, copy made in /foo/bar.log.2001-02-16)
> - logging continues in /foo/bar.log after each copy is made (ie this file
> keeps growing)
> No mention is made of emptying /foo/bar.log.
> I assume that at some point (in this example daily) the /foo/bar.log is
> emptied, so is:
> - /foo/bar.log moved to /foo/bar.log.2001-02-16 and a new /foo/bar.log
> created?
> or
> - /foo/bar.log copied to /foo/bar.log.2001-02-16, then that content
> deleted from /foo/bar.log?
> If the actual mechanics are not required then the simplest might be to
> replace "copied" with "moved" in the current statement.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
