Hi everybody,
from the manual:
================================================
Finally, the mandatory configuration file is read, if you specified one when
you compiled the program. This is a configuration file which cannot be overridden
by the user: if it is not found, analog exits immediately. This allows a
system administrator to prevent users analysing certain files or producing
certain reports, for example...
================================================
Ok... let's say we're analysing a site -- except cron jobs and cmd -- through
the CGI interface, have a config file that tells Analog to read 213 log files,
let's say going back 2 years... the one (and only?) obvious problem is with
users trying to (sometimes without knowing about it) analyse all the log
files... which we do not want. Of course we only want them to be able to
analyse, let's say last month data...
But -- if we put something like
FROM -00-00-30
TO -00-00-01
in the mandatory config file, it will not work for us if a user wants to analyse
let's say last 2 days (his 2 day requirement would get overwritten by 30
days from the mandatory config file)... any ideas?
I know there would be ways around it... but I can't think of a good one...
Any ideas, amigos?
Josef D.
------------------------------------------------------------------------
This is the analog-help mailing list. To unsubscribe from this
mailing list, send mail to [EMAIL PROTECTED]
with "unsubscribe" in the main BODY OF THE MESSAGE.
List archived at http://www.mail-archive.com/[email protected]/
------------------------------------------------------------------------
