On Wed, 5 Oct 2005, Chris Sharman wrote:
The naming scheme used is surely known to analog via the LOGFILE
statement ? And is surely effectively the same thing as the rotation
schedule ?
Eg LOGFILE sys$disk:[]access_log_combined_%Y-%M-%D.gz;*
would be daily files, from midnight
But this is absolutely not typical. It's normal to rotate at 2am or 3am.
Then this logfile covers some of the stated day and some of the previous
day. So you'd have to include it if you wanted a report for either day.
Another common scheme is that logfiles are only rotated weekly, but named
after the day on which they're rotated. So if you want any part of the
preceding week, you have to read this logfile.
And don't get me started on timezones.
Analog simply has no way to know this stuff without built-in knowledge of
the rotation schedule used, and of the naming of the logfiles when they
cover a certain time span.
--
Stephen Turner, Cambridge, UK http://homepage.ntlworld.com/adelie/stephen/
"Low Priced Cambridge Clare College. Big selection at eBay UK!"
(Ad after Google search for Clare College Cambridge)
+------------------------------------------------------------------------
| 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
+------------------------------------------------------------------------
