A 'search targets' report would help with this, and would be a good thing in its own right, detailing search engine hits.
See http://analog.cx/docs/faq.html#faq128
Another Enhancement request:
the "logfile blah-%Y-%M.log.gz" command just picks up the file containing the 'to' date - how hard would it be to scroll round every year/month/week/day between from & to, reporting all of them - would be an improvement. The logic to start at to, and loop back to from (or vice versa) generating and using all the logfiles, would be straightforward enough - you'd search the string for %n, %h, %D|%w, %m|%M, %y|%Y, and set your step size accordingly.
In some environments, logs get rotated every three or six hours. Would you suggest that if the LOGFILE command has a %h in it, it should try every hour in every day? Does it really need to support minutes?
-- Jeremy Wadsack Seven Simple Machines
+------------------------------------------------------------------------ | TO UNSUBSCRIBE from this list: | http://lists.meer.net/mailman/listinfo/analog-help | | Usenet version: news://news.gmane.org/gmane.comp.web.analog.general | List archives: http://www.analog.cx/docs/mailing.html#listarchives +------------------------------------------------------------------------
