7:54:46 : ----------------------------------------------------------
0m 0.0s : Pike v7.0 release 230, Roxen WebServer 2.1.130
: Loading pike modules ... Done [855.0ms]
: Loading roxen ... Done [7884.8ms]
: Loading font handlers ...
: Builtin fonts (scalable)
7:54:55 : Compact image file font (bitmap)
0m 9.5s : Image directory fonts (bitmap)
: Image TAR-file fonts (bitmap)
: Compatibility bitmap fonts (bitmap)
: TTF fonts (scalable)
: Done [516.5ms]
7:54:56 : Adding languages ... Done [45.05ms]
0m 9.7s : Initiating argument cache ... Done [101.31ms]
:
: Enabling the configuration Administration Interface ...
: Registered http://*:27474/ for Administration Interface
: Enabled Administration Interface in 412.1ms
7:54:56 : Starting 5 threads to handle requests.
0m10.2s : -- Total boot time 10.2 seconds ---------------------------
:
: ** 2000-09-20 07:54 pid: 15469 ppid: 15460 uid: wing
|
Beginning of debug log
The debug log is available as roxen/logs/debug/default.1. The
debug log contains essentially the same information as the event log, but
in a text only format. It is sent either to a file or to syslog on a unix
system. This is controlled by the Logging / Debug log method variable
under the Globals tab.
The debug log is important when the server starts, since it writes
messages before the administration interface becomes available. If the
server did not restart properly the debug log will show why.
The debug log also contains the process id of the Roxen process and the
start script process. This information is important if you want to restart the server
without using the admin interface, for instance by using the kill command instead.
