Re: Command Line processing question
"Aengus" <[email protected]>
| Newsgroups | gmane.comp.web.analog.general |
|---|---|
| Message-ID | <17567CA5138447FE864D551A8EDB8BC6@WC515ALawlo> |
Terry Chambers <[email protected]> wrote: >> My site's log files are multiple .gz files each day (about 30 of >> them). I want to create a command line to perform the analog >> process. Herei s my example: >> >> >> /analog-6.0/analog -G +g/analog/configs/analog-daily-full.cfg logfile >> /www_logs/2008/07/09/*.gz O /www_reports/daily/20080709.html >> >> >> When I execute this, Analog complains that it cannot understand the >> log format of the files. >> >> When I embed the location of the LOGFILE and OUTFILE into the CFG >> file, it works fine. >> >> Is there a problem with my command line? Is the problem in my >> config file itself? "LOGFILE" is sort of assumed on the command line. For example analog 20080714.log will analyze 20080714.log. To specify the outfile, the command line argument is +O, and, just like the +g for yoru additional .cfg file, there shouldn't be a space between the +O and the outfile. /analog-6.0/analog -G +g/analog/configs/analog-daily-full.cfg /www_logs/2008/07/09/*.gz +O/www_reports/daily/20080709.html http://analog.cx/docs/syntax.html http://analog.cx/docs/indx.html#clargs Aengus +------------------------------------------------------------------------ | 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 +------------------------------------------------------------------------