ravikumar at staff
Jul 15, 2008, 11:45 PM
Post #5 of 5
(684 views)
Permalink
|
analog-help-request [at] lists wrote:
> >Send analog-help mailing list submissions to
> analog-help [at] lists
>
>To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.meer.net/mailman/listinfo/analog-help
>or, via email, send a message with subject or body 'help' to
> analog-help-request [at] lists
>
>You can reach the person managing the list at
> analog-help-owner [at] lists
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of analog-help digest..."
>
>
>Today's Topics:
>
> 1. Command Line processing question (Terry Chambers)
> 2. RE: Command Line processing question (Jeremy Wadsack)
> 3. Re: Command Line processing question (Stephen Turner)
> 4. Re: Command Line processing question (Aengus)
>
>
>----------------------------------------------------------------------
>
>Message: 1
>Date: Mon, 14 Jul 2008 18:40:42 -0400
>From: "Terry Chambers" <terry.chambers [at] gmail>
>Subject: [analog-help] Command Line processing question
>To: analog-help [at] lists
>Message-ID:
> <87d1d5cc0807141540q482458a4j9285a560d4b75693 [at] mail>
>Content-Type: text/plain; charset="iso-8859-1"
>
>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?
>
>Thanks
>Terry
>-------------- next part --------------
>An HTML attachment was scrubbed...
>URL:
http://lists.meer.net/pipermail/analog-help/attachments/20080714/82f2ad02/attach
ment-0001.html
>
>------------------------------
>
>Message: 2
>Date: Mon, 14 Jul 2008 15:48:22 -0700
>From: Jeremy Wadsack <jeremy [at] 7simplemachines>
>Subject: RE: [analog-help] Command Line processing question
>To: Support for analog web log analyzer <analog-help [at] lists>
>Message-ID:
> <3A3310C165D9CD4CA6AAC4A3071834981526C34B [at] hobbes>
>Content-Type: text/plain; charset="us-ascii"
>
>Likely you have a "LOGFORMAT" command in your configuration file. That only
applies to log files in the same config file (and the command line is
considered a separate config file). If you change that the "DEFAULTLOGFORMAT"
that should apply to all log file statements, including the command line.
>
>--
>
>Jeremy Wadsack
>Seven Simple Machines
>________________________________
>From: analog-help-bounces [at] lists
[mailto:analog-help-bounces [at] lists] On Behalf Of Terry Chambers
>Sent: Monday, July 14, 2008 3:41 PM
>To: analog-help [at] lists
>Subject: [analog-help] Command Line processing question
>
>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?
>
>Thanks
>Terry
>
>
>
>-------------- next part --------------
>An HTML attachment was scrubbed...
>URL:
http://lists.meer.net/pipermail/analog-help/attachments/20080714/180d0692/attach
ment-0001.html
>
>------------------------------
>
>Message: 3
>Date: Mon, 14 Jul 2008 23:51:09 +0100
>From: "Stephen Turner" <analog-author [at] lists>
>Subject: Re: [analog-help] Command Line processing question
>To: "Support for analog web log analyzer" <analog-help [at] lists>
>Message-ID:
> <40e7475b0807141551w748a876ar7cd1ae0b800f57a3 [at] mail>
>Content-Type: text/plain; charset=ISO-8859-1
>
>2008/7/14 Terry Chambers <terry.chambers [at] gmail>:
>> 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?
>>
>
>You probably have a LOGFORMAT in the cfg file, which only applies to
>LOGFILEs in that same cfg file. You need to put the LOGFORMAT on the
>command line, before the logfiles, or else use DEFAULTLOGFORMAT in the
>cfg file.
>
>--
>Stephen Turner
>
>
>------------------------------
>
>Message: 4
>Date: Mon, 14 Jul 2008 19:00:47 -0400
>From: "Aengus" <analog07 [at] eircom>
>Subject: Re: [analog-help] Command Line processing question
>To: "Support for analog web log analyzer" <analog-help [at] lists>
>Message-ID: <17567CA5138447FE864D551A8EDB8BC6 [at] WC515ALawl>
>Content-Type: text/plain; charset="iso-8859-1"
>
>Terry Chambers <terry.chambers [at] gmail> 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
>|
>| Usenet version: news://news.gmane.org/gmane.comp.web.analog.general
>| List archives: http://www.analog.cx/docs/mailing.html#listarchives
>+------------------------------------------------------------------------
>
>
>End of analog-help Digest, Vol 47, Issue 10
>*******************************************
You should provide configuration file with full path or relative to the location from where you are executing this command.
the fragment +g/analog/configs/analog-daily-full.cfg should be like +ganalog/configs/analog-daily-full.cfg ,if you are executing this command whose sub-directory is analog/configs/ . The '/' after +g is not ok. It is good if you can always give full-path from root like /home/analog.....
It is always advisable to follow good conventions while dealing from command line. So try following edited command.
analog -G +ganalog/configs/analog-daily-full.cfg +C"LOGFILE /www_logs/2008/07/09/*.gz" +C"OUTFILE /www_reports/daily/20080709.html"
Remember try to give full path for configuration file, log file and output file as well.
Warm Regards
-ravikumar kakde.
|
