Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: cron/logrotate
- To: tlug@example.com
- Subject: Re: cron/logrotate
- From: Darren Cook <darrenj@example.com>
- Date: Tue, 05 Jun 2001 12:52:51 +0900
- Content-Transfer-Encoding: 7bit
- Content-Type: text/plain; charset=iso-2022-jp
- References: <F203gtZKpjE5aHaZVrD0001d7e0@example.com>
- Reply-To: tlug@example.com
- Resent-From: tlug@example.com
- Resent-Message-ID: <8y7wCD.A.nQ.PeFH7@example.com>
- Resent-Sender: tlug-request@example.com
> > > 7.6M Jun 2 23:43 access_log.1 > > > Which leads me to ask, "why was it rotated at 23:43" when the crontab > specifically runs cron.daily (which rotatelogs is called from) at 4:02am? What I meant was that when the log is rotated it doesn't alter the datestamp. So your access log had it's last hit at 23:43, so that was the datestamp at 4:02am when it was rotated (i.e. renamed). This implies you had no hits between 23:43 and 4am. Also, if you gzip the files, the datestamp will still stay as 23:43. Darren
- References:
- Re: cron/logrotate
- From: "Jean-Christian Imbeault" <jean_christian@example.com>
Home | Main Index | Thread Index
- Prev by Date: Re: cron/logrotate
- Next by Date: Re: cron/logrotate
- Prev by thread: Re: cron/logrotate
- Next by thread: Re: cron/logrotate
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links