Oops - probably sent my "subscribe" message(s) to the list itself. Sorry.
I've got an HTML page that allows users to select the logfile dates they want Analog
to use. The HTML page goes to a Perl script, which does a bit of manipulation with
the dates before passing them on to Analog. (The reason for the manipulation is
because we keep a years worth of compressed logfiles on the server. Rather than point
Analog to "access*.gz", Perl figures out which logfiles Analog will REALLY need based
on the HTML form, and passes Analog only the LOGFILE directives that it needs. (e.g.
'LOGFILE access-10-Sep-1999*.gz,access-11-Sep-1999*.gz') Much faster that way.)
The problem is that the date comes in from the form as a 2-digit year, in keeping with
Analog's TO/FROM directives format of YYMMDD . In order for me to convert it to a
4-digit date, I have to prepend a "19" to $date if $date >= 70, or "20" if $date < 70 .
It works OK, and another solution would be for the HTML form to pass a 4-digit date
which I could work with, then chop of the leading 2 digits before giving it to Analog.
But might it not make more sense for Analog to use an (optional) YYYYMMDD format for
the TO/FROM directives?
Thanks.
--== Sent via Deja.com http://www.deja.com/ ==--
Share what you know. Learn what you don't.
------------------------------------------------------------------------
This is the analog-help mailing list. To unsubscribe from this
mailing list, send mail to [EMAIL PROTECTED]
with "unsubscribe analog-help" in the main BODY OF THE MESSAGE.
List archived at http://www.mail-archive.com/[email protected]/
------------------------------------------------------------------------
