On Tue, 11 Nov 2003, Tim Larson wrote:That's what I'm doing now. Not hard, just tedious. And seemingly unnecessary since I supply the from and to dates, a log name format, and we happen to have a calendar system with consistent rules. It feels like I'm giving someone a map and instructions to drive from here to Chicago, but still having to specify right|left|straight for every intersection along the way.
Yes, but the problem is, you use one logfile naming convention, but other people use other conventions. Imagine if you only rotated your logfiles weekly, for example -- the rules would be different. The only alternative would be for you to specify in the config file the date range covered by each logfile, which would be just as tedious.
OK, I see that if you name based on week (200301.log - 200353.log; or w031101.log, w031108.log, etc) or some other convention, then the from/to used for reporting span would not work. Maybe there'd have to be a second set of from/to to capture the right logs, then use the existing from/to to process records within those logs. But if you're using date-based naming at all, there's got to be something better than simple wildcarding.
Maybe I will write a patch. If you like it, you can incorporate it. :)
Tim -- Tim Larson, Webmaster LovelySkin.com 402.334.SKIN For a more beautiful you, surf us!
+------------------------------------------------------------------------ | TO UNSUBSCRIBE from this list: | http://lists.isite.net/listgate/analog-help/unsubscribe.html | | Digest version: http://lists.isite.net/listgate/analog-help-digest/ | Usenet version: news://news.gmane.org/gmane.comp.web.analog.general | List archives: http://www.analog.cx/docs/mailing.html#listarchives +------------------------------------------------------------------------
