Ron Savage wrote:
> Background: I compiled analog without editing anlghead.h. I'm using V
> 4.13
> under Linux.
>
> 1) This page:
> http://www.ron.ozstores.com/~rons/analog-docs/logfmt.html
> should, I think, state more explicitly that analog uses these
> special
> characters (%s, %S, ...), and constants (-, "-", ...) in the LOGFORMAT
>
> option to match the format of lines in the log file,
>
Doesn't this say that?
"In other words, it's just the sample line but with the hostname
replaced by %S, the username by %u etc."
> _and_ that analog can
> extract fields from the log file line and populate things like %v, so
> that
> the user can use %v elsewhere, eg in the LOGFILE command, and have
> analog
> supply a value for %v which analog ahs taken from a log file line.
>
>From docs/logfile.html, "The argument can contain a %v, and the name of
the virtual host will then be inserted at that point." But I agree that
it could mention where the virtual host information must come from.
> 4) This page:
> http://www.ron.ozstores.com/~rons/analog-docs/logfmt.html
> says "you will probably find it more convenient to use
> APACHEFORMAT". Joke.
> This stmt caused much grief. We use Apache, with this
> LogFormat commamd:
> LogFormat "%v %h %l %u %t \"%r\" %>s %b \"%{Referer}i\"
> \"%{User-Agent}i\""
> combined
> (although I ended up needing 12 LOGFORMAT commands of various
> patterns.
> That's my problem.)
> However analog runs fine if I use LOGFORMAT. It gives me
> '... large number of corrupt lines...' if I change all these
> to
> APACHELOGFORMAT.
> Why is this?
>
Because APACHELOGFORMAT lines use Apache's LogFormat tokens not
Analog's. You would need to write a line like
APACHELOGFORMAT ("%v %h %l %u %t \"%r\" %>s %b \"%{Referer}i\"
\"%{User-Agent}i\"")
> 5) This page: http://www.ron.ozstores.com/~rons/analog-docs/debug.html
>
> contains this line:
> The WARNINGS command acts similarly to the DEBUG command...
> but this section _doesn't actually say_ how to use the
> WARNINGS ON line (eg
> all by itself),
>
I think that's because, "By default all warnings are on." Also, I would
argue that the saying it acts similarly to the DEBUG command does
explain how to use it: Use ON for all on, OFF for all OFF or +/- letter
for each type.
> 6) When I use WARNINGS -R, the very first output line:
> ./analog: analog version 4.13/Unix
> is suppressed. Is this deliberate?
When there's no error or warning messages, then the header is
suppressed. This is normal Unix behavior (so if you run it as a cron job
outputting to email you don't get emails when everything works fine).
If you got messages, but no header, then this is probably a bug.
> 7) The docs don't clearly warn the me that if I install analog in one
> dir
> and I output to a different dir, and then try to use a browser to view
> the
> output, I need 2 copies of the lang and images dirs, one for analog to
> use
> at run time and one for the browser to use a view time.
>
That's because you don't. You only need language files for Analog when
it's run. When you look at the report that is created all the language
elements are inserted already. You DO need to have a fully qualified
path to your language files when you run the anlgform interface, but
this is specified in the docs and both form files.
BTW, I agree with the rest of your points.
Jeremy Wadsack
Wadsack-Allen Digital Group
------------------------------------------------------------------------
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]/
------------------------------------------------------------------------
