cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Berin Loritsch <blorit...@apache.org>
Subject LogKit targets in webapp
Date Wed, 12 Dec 2001 16:36:05 GMT
Trying to figure out which log you should look in while trying to track
down errors is kind of a crap shoot with the current names:

root.log
cocoon.log
component.log

These names do not have meaning to an administrator.  Typically, web servers
will separate the log files into something with semantic meaning.  For
instance, Apache HTTPD separates the log files into:

access.log
error.log

The Access.log file has the recorded information of who accessed what and
when.  The error.log file has any error messages from the HTTPD server or
any of it's modules (or CGI scripts).  This is simple and effective.

We should adopt a file naming strategy that makes sense to a user.  The
actual categories that are mapped are "xslt", "root", and "cocoon".  Again,
these are not the best, but they do provide more of an idea of the logger
types.

I would like to see the equivalent of the "access.log" to handle all the
CocoonServlet messages.  This is useful in itself.

I know this is all configurable, but I would like us to lead by example.
For example, provide the following categories:

"core"     - information from the core components
"sitemap"  - information from the sitemap components
"access"   - information from the CocoonServlet class.

With equivalent log files.  In the end, this will prove to be more effective
as you can more authoritatively state which logfile to look in when assisting
others with installation problems.

-- 

"They that give up essential liberty to obtain a little temporary safety
  deserve neither liberty nor safety."
                 - Benjamin Franklin


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message