Table of Contents
Introduction
Installation
Handling Challenger
Virtual Servers
Configuration Examples
Modules
Filesystems
RXML Tags
Graphics
Proxy
Databases
Miscellaneous Modules
Security Considerations
Scripting
Frontpage
Upgrading
Third Party Extensions
Portability
Reporting Bugs
Appendix
|
Logs
Challenger provides access log files in the Common Log Format
for each virtual server. It is possible to configure exactly
what should be logged and how by the Server Variables/Logging... variables.
Logging can also be done through special logging modules. A few
such modules are included with Challenger.
User logger
Logs accesses to a user's home pages in a separate access log. Each
user that wants such an access log must create an AccessLog
file, in her home page directory.
- AccessLog filename
-
The filename of the access log file, by default AccessLog.
- Logging Format
-
Configuration of how things should be logged.
- Only log in userlog
-
If set, no entry will be written in the normal log.
- Private logs
-
The directories that are to get their
own log files. Either use a specified PATH or a
pattern. /foo/ will use /foo/AccessLog,
/users/%s/ will use an AccessLog in all user
directories, providing that the users directories are mounted on
/users/. All PATH's are relative to Challenger's virtual
filesystem.
Logging disabler
This module can be used to turn off logging of files, specified with a
regexp.
- Logging for
-
All files whose PATH in the virtual filesystem match these patterns
will be logged, unless they match any of the No logging for
patterns.
- No logging for
-
All files whose PATH in the virtual filesystem match these patterns
will be excluded from logging.
Client logger
This module simply logs the user-agent field in a
log file. Normally, this field is not logged in access logs, but it is
possible to configure Challenger to log it there.
- Client log file
-
The file to log to.
|