LOGFORMAT only applies to LOGFILE commands in the same configuration
file (the command line is considered a separate config file). Use
DEFAULTLOGFORMAT for this. See http://analog.cx/docs/logfmt.html for
details.
--
Jeremy Wadsack
Seven Simple Machines
Curry, Timothy M. wrote:
We're running Analog 6.0 and running reports on multiple hosted web
sites.
The global.cfg contains the following logformat commands...
LOGFORMAT COMBINED
LOGFORMAT (%S %j %j [%d/%M/%Y:%h:%n:%j -%j] "%j%w%r%w%j" %c %b "%f" "%B"
"%u")
...but no LOGFILE command.
Since we're running ~separate~ reports for multiple web sites, we have a
driver script that specifies the LOGFILE in the command line it
generates for each of the sites. (the apache access logs are rotated
weekly, BTW).
Problem is, the custom LOGFORMAT doesn't appear to apply to those sites
which use it. I keep getting "Warning F: Can't auto-detect format of
logfile" in the errors<host-name-here>.txt file. Also, I get a "Warning
D: LOGFORMAT in configuration file ... With no subsequent LOGFILE"
error.
However, if I run the command by hand on the command line and specify
+C'LOGFORMAT (%S %j %j [%d/%M/%Y:%h:%n:%j -%j] "%j%w%r%w%j" %c %b "%f"
"%B" "%u")' as part of the command line before +C'LOGFILE ...', it works
just fine.
Am I correct in thinking that Analog is ignoring the custom LOGFORMAT
because there's no LOGFILE command in the global.cfg? (The COMBINED
format being built-in is, of course, always recognized -? )
I would greatly prefer not to have to specify a custom LOGFORMAT for
those sites we host which have a non-COMBINED log format on the command
line.
Any way around this?
-T.Mike
+------------------------------------------------------------------------
| 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
+------------------------------------------------------------------------
