On 2 May 2007, at 0:11, Aengus wrote:
From your initial description, I imagine that the .gz files are the
"rotated" logs - they are "done" and don't overlap. You could consider
the .log files as "temporary", constantly being updated until the
end of
the day, when it is gzipped, and a new .log is created. In that
situation, you only want to archive the .gz files.
That's a fairly common scenario for managing web server logs - I'd be
surprised if your server is using .log and .gz files any differently.
Thank you - I had a lack of understanding of how the log files were
processed by the server. So in the case of a server which rotates the
files on a weekly basis, I just download log.1.gz every week. If I
happen to miss it one week, then next week it will have been rotated
to log.2.gz. I think!
I then create an archive of the log.1.gz files to run through Analog.
Is that broadly correct?
--
Mick Burrell
+------------------------------------------------------------------------
| TO UNSUBSCRIBE from this list:
| http://lists.meer.net/mailman/listinfo/analog-help
|
| Analog Documentation: http://analog.cx/docs/Readme.html
| List archives: http://www.analog.cx/docs/mailing.html#listarchives
| Usenet version: news://news.gmane.org/gmane.comp.web.analog.general
+------------------------------------------------------------------------
