"Bob Puff@NLE" wrote:
> > Also, the above (without typos) ships in almost every default Apache install, but
>may not be the way a user want to
> > configure apache.
>
> What typos? That's exactly what I have now, running. And no, it is NOT the default
>Apache setting - I had to add the %v in there.
I stand corrected. I didn't see the %v (which of course was the whole point of the
thread). What I meant by typos, was:
LogFormat "%h %l %t \"%r\" %>s %b %v \"%{referer}i\" \"%{user-Agent}i\""
combination
CustomLog logs/access_log combined
Will produce a logformat in "combined" format (assumably defined elsewhere in your
httpd.conf). Not the "combination" logformat that you want. I has assumed that you
meant
to write
CustomLog logs/access_log combination
> The biggest thing the online docs need are examples, and defaults.
Well, docs/logfmt.html has examples. docs/report.html is examples. There are also some
(limited, yes, but some) examples in examples directory.
> For example, if none of the reports are expressly turned on or off, what reports are
>generated by default?
>
> For each of the different reports, what are the valid COLS commands for them? What
>are the default COLS?
Both of these items can be gleaned from reading the examples/big.cfg file that ships
with the distribution. But I agree, that this should be documented in the docs as
well.
> In the FAQ, I'm sure many users would benefit from the main question I had: How come
>the Virtual Domain report doesn't work? The answer turned out to be three things:
>
> 1. Add a VHOST ON in /etc/analog.cfg
> 2. Modify Apache's httpd.conf file as shown above to log the vhost domain
> 3. Define LOGFORMAT in /etc/analog.cfg as shown above.
What, item D7 isn't helpful enough:
7.I host lots of virtual domains. How should I set up analog?
There's a file in the examples directory which discusses this issue.
: - )
> There are a lot of us newbies out there that just need a little more direction than
>man pages without examples.
Such as a (well written) HOWTO? Man pages are generally designed to work as
references. The Analog docs are designed to be a guide (with reference ability through
the
index and report references). Perhaps a series of good HOWTOs would be helpful to the
Analog community. Does any one on the list have experience in technical writing and
want to donate their time?
"Chris D.Halverson" wrote:
> Then help the "cause" and write documentation. Analog is written by a
> developer (duh!), not a writer. I'm able to grok what I need out of
> it, but sometimes it takes some investigation. Projects like these,
> ie. free ones, usually need better docs, however, the developers are
> rarely the "best" choice for this job as they are too intimate with
> the product and "know" how it's supposed to work, and/or they just
> aren't good writers.
As a developer who also writes his own documentation, I will say what all developers
say: No matter how good or bad I may be at documentation, writing user docs is not as
fun as writing code. So it becomes last priority. <off-topic> The open-source
community could be helped greatly by technical writers (there are people out there who
think
writing users docs is fun, right?) donated some of their time to the
projects.</off-topic>
> That being said, the docs are pretty good, just very technical.
I disagree (sorry, no offense Stephen, but I suppose that's why you're a post-doc in
statistics not technical writing). I think the organization of the docs is hard to
understand. On the other hand, I view the world in a different way that you, Chris or
Bob, (or Stephen or anyone else). That's why well documented products allow you to
learn in different ways. And well designed products don't require documentation (but
still provide it all). At least that's the goal. Most consumer products are like this
(your toaster came with a manual, but you never had to read it). Most consumer
products are exceedingly less complicated as well.
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]/
------------------------------------------------------------------------
