- an application/error log that traces errors or other application-level messages
Your application may leverage that second logger by calling
Both logs are writing to files identified by the following keys
-- `log.access_file` for incoming requests using the
+- `log.access_file` for incoming requests using the
`common log format <http://en.wikipedia.org/wiki/Common_Log_Format>`_
-- `log.error_file` for the other log
+- ``log.error_file`` for the other log
+ Refer to the :mod:`cherrypy._cplogging` module for more
+ details about CherryPy's logging architecture.
-You may be interested in disabling either logs. To do so, simply
-set a en empty string to the `log.access_file` or `log.error_file`
+You may be interested in disabling either logs.
+To disable file logging, simply set a en empty string to the
+``log.access_file`` or ``log.error_file`` keys in your
+:ref:`global configuration <globalsettings>`.
+To disable, console logging, set ``log.screen`` to `False`.
Play along with your other loggers
CherryPy comes with a fine-grained configuration mechanism and
settings can be set at various levels.
identifier used by CherryPy to load the user's session from
+ Refer to the :mod:`cherrypy.lib.sessions` module for more
+ details about the session interface and implementation.
+ Notabley you will learn about sessions expiricy.