I hope it's allowable to modify the subject and pick up on this thread and
go off in slightly different direction:
I'm running Analog 3.32 on a UNIX/Apache/Intel Linux box.
Most of the discussion here seems to deal with running Analog from the
command line, and very little discussion seems to deal with the combo
anlgform.cgi, and anlgform.html.
In the html, the following line is used;
<form action="/cgi-bin/anlgform.cgi" method="GET">
can a different *.cfg be called here, and how? Or;
How about the following line in the html:
<!-- input type=hidden name="lo"
value="/usr/local/etc/httpd/logs/access_log" -->
Can this be used to call a different logfile? Duh! It looks that way. Then
just edit analog.h thus:
#define DEFAULTCONFIGFILE "none"
Right now I'm just trying to get analog to run for 70 virtual domain
users--my idea is to place a different/modified html into each of the 70
virtual user passwd protected areas like, /WWW/Stats.
Then run one /etc/httpd/analog, and one /home/httpd/cgi-bin/anlgform.cgi.......
Same question as the thread, different approach--thanks,
Joe
At 04:18 PM 10/28/1999 , you wrote:
>At 15:25 10/28/99 +0100, you wrote:
>
>>It's 50 but you can change it in analhead.h.
>>
>
>Thanks, I knew I had seen that somewhere.
>
>>But you will only get one output this way. That may not be your intention.
>>To get lots of output files you have to run analog lots of times.
>>
>>If you download version 3.9, there is an example in the examples directory
>>about this.
>>
>
>I'll get version 3.9 and take a look. I was not, perhaps, very clear in
>the original - I meant each of the numerous config files to each contain a
>new/different LOGFILE address and OUTFILE address, ie.,
>
>> CONFIGFILE /home/sites/site2/logs/site2.cfg
>
>site2.cfg
>HOSTNAME "Home of Site 2"
>LOGFILE /home/sites/site2/logs/access
>OUTFILE /home/sites/www.site2.com/stats/index.html
>
>Thus, the majority of the configuration for a "standard" analog output
>would reside in analog.cfg, with these three lines (and perhaps one or two
>more) in a config file tailored (barely) for each domain.
>
>This would result in numerous runs of analog, wouldn't it? If things get
>to taking too long (not a danger right at the moment), I could always set
>up monday.cfg, tuesday.cfg, wednesday.cfg, etc. (I intend to run analog
>only once a week per site.)
>
> - fleet -
>
>------------------------------------------------------------------------
>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]/
>------------------------------------------------------------------------
------------------------------------------------------------------------
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]/
------------------------------------------------------------------------
