Bug 50770

Summary: a rotatelogs issue, if time changed
Product: Apache httpd-2 Reporter: Kim Yong Hwan <knight>
Component: supportAssignee: Apache HTTPD Bugs Mailing List <bugs>
Status: RESOLVED LATER    
Severity: normal Keywords: MassUpdate
Priority: P2    
Version: 2.2.17   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Attachments: changed rotatlogs-source.

Description Kim Yong Hwan 2011-02-14 03:20:28 UTC
Created attachment 26647 [details]
changed rotatlogs-source.

Hello.

When time changed from past to future, function of rotatelogs is well working.
But, When time changed from future to past, rotatelogs is not working

This is a example below.
#] date
2011. 02. 14. (mon) 17:04:31 KST

#] ./rotatelogs aaa-%y%m%d 86400
1
2
3
  (on other terminal, I runed 'date 112001002007'.)
changed
^D

#] ls -al aaa*
-rw-r--r--  1 root root 14 11/20 01:00 aaa-110214
   (I expected rotatelogs would rotate logs, but it is not splitted!!!!)


So. I made a patch for this. I know this patch is not pretty. :)
I patched and uploaded rotatlogs.c in http 2.2.13. 

After installing, I tested it.

#] date
2011. 02. 14. (mon) 17:10:31 KST

#] ./rotatelogs aaa-%y%m%d 86400
1
2
3
  (on other terminal, I runed 'date 112001002007'.)
changed
^D

#] ls -al aaa*
-rw-r--r--  1 root root       8 11/20 01:00 aaa-071119
-rw-r--r--  1 root root       6  2/14  2011 aaa-110214
  (This was what I wanted.)

Sometimes CMOS of servers do not work well, Time information could be moved to past or future. 
Could you check the function of rotatelogs that I mentioned?
Comment 1 William A. Rowe Jr. 2018-11-07 21:09:43 UTC
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd.

As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd.

If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question.

If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with.

Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.