You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 

57 lines
1.8 KiB

<?xml version="1.0" encoding="UTF-8"?>
<module xmlns="urn:lighttpd.net:lighttpd2/doc1">
<short>
offers various utilities to aid you debug a problem.
</short>
<action name="debug.show_connections">
<short>shows a page similar to the one from mod_status, listing all active connections</short>
<description>
By specifying one or more "connection ids" via querystring (parameter "con"), one can request additional debug output for specific connections.
</description>
<example>
<config>
if req.path == "/debug/connections" { debug.show_connections; }
</config>
</example>
</action>
<action name="debug.profiler_dump">
<short>dumps all allocated memory to the profiler output file if profiling enabled</short>
<description>
<textile>
lighttpd2 needs to be compiled with profiler support, and profiling has to be enabled by setting the environment variable @LIGHTY_PROFILE_MEM@ to the path of a target log file.
</textile>
</description>
</action>
<action name="debug.show_events">
<short>shows a plain text list of all events</short>
<description>
this is a very low level debug tool for developers.
</description>
<example>
<config>
if req.path == "/debug/events" { debug.show_events; }
</config>
</example>
</action>
<setup name="debug.show_events_after_shutdown">
<short>time in seconds after start of shutdown to log remaining active events</short>
<parameter name="timeout">
<short>timeout after which to display events (default: disabled)</short>
</parameter>
<description>
this is a very low level debug tool for developers; it shows which event listeners keep lighttpd2 alive when it should stop.
</description>
<example>
<config>
setup { debug.show_events_after_shutdown 5; }
</config>
</example>
</setup>
</module>