https://bz.apache.org/bugzilla/show_bug.cgi?id=65980
Bug ID: 65980
Summary: clarify rotatelogs -n and maybe improve truncation
Product: Apache httpd-2
Version: 2.5-HEAD
Hardware: PC
OS: Mac OS X 10.1
Status: NEW
Severity: normal
Priority: P2
Component: Core
Assignee: bugs@httpd.apache.org
Reporter: covener@gmail.com
Target Milestone: ---
rotatelogs -n has some surprising behavior with size-based logging and
pre-existing logfiles when -t isn't provided.
Truncation of "logfile" the first pass through only occurs with -t, but
truncation of other files (or wrapping back around to "logfile") is always
done.
So without -t, and size-based rotation and e.g. -n 5, at a subsequent startup
logfile may be at max size and logfile.1 at 1/2 size. Currently, logfile will
be skipped over and on the first doRotate() logfile.1 will be truncated. The
loss of the first half of logfile.1 is surprising and could be dodged in this
scenario.
An option:
If using -n and not -t, hunt for an unused .N and start there. Or specifically
if size-based rotation is used, append to the first one that isn't at/beyond
the size limit already. This hunting could open the file without truncating
and use the existing checkRotate()
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org
Bug ID: 65980
Summary: clarify rotatelogs -n and maybe improve truncation
Product: Apache httpd-2
Version: 2.5-HEAD
Hardware: PC
OS: Mac OS X 10.1
Status: NEW
Severity: normal
Priority: P2
Component: Core
Assignee: bugs@httpd.apache.org
Reporter: covener@gmail.com
Target Milestone: ---
rotatelogs -n has some surprising behavior with size-based logging and
pre-existing logfiles when -t isn't provided.
Truncation of "logfile" the first pass through only occurs with -t, but
truncation of other files (or wrapping back around to "logfile") is always
done.
So without -t, and size-based rotation and e.g. -n 5, at a subsequent startup
logfile may be at max size and logfile.1 at 1/2 size. Currently, logfile will
be skipped over and on the first doRotate() logfile.1 will be truncated. The
loss of the first half of logfile.1 is surprising and could be dodged in this
scenario.
An option:
If using -n and not -t, hunt for an unused .N and start there. Or specifically
if size-based rotation is used, append to the first one that isn't at/beyond
the size limit already. This hunting could open the file without truncating
and use the existing checkRotate()
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org