![]() ![]() LiteSpeed will ask you for certain “Personal Information” when you complete registration or product information request forms on the Site, including but not limited to your name, address, telephone number, email address, and credit card information. IF YOU DO NOT AGREE WITH ANY OF THE TERMS BELOW, YOU SHOULD NOT USE THIS SITE OR THE PRODUCTS OR SERVICES OFFERED BY LITESPEED TECHNOLOGIES AT THIS SITE. LiteSpeed encourages you to review this Privacy Policy periodically for any changes. If we make changes to this Privacy Policy, we will update the Effective Date to note the date of such changes. LiteSpeed reserves the right to revise, modify, add, or remove provisions to this Privacy Policy at any time. By using this Site or any products or services provided through the Site, you expressly consent to the use and disclosure of information as described in this Privacy Policy. ![]() You can visit most pages of the Site without giving us any information about yourself, but sometimes we do need information to provide services that you request. This policy ("Privacy Policy" or "Policy") explains our practices for our site, ("Site"). (aka “LiteSpeed”) is committed to protecting your privacy. It is possible to lose log data if external loggers cannot keep up with the speed and volume of the log stream. If a logger crashes, the web server will start another instance but the log data in the stream buffer will be lost. ![]() Only when one logger application fails to process access log entries in time will the server attempt to spawn another instance of the logger application. LiteSpeed server always attempts to keep the number of logger applications as low as possible. LiteSpeed web server performs simple load balancing among multiple logger applications if more than one instance of a logger application is configured. This means it will execute as the user ID specified in the virtual host's External App Set UID Mode settings and will never run on behalf of a privileged user. The logger process is spawned in the same way as other external (CGI/FastCGI/LSAPI) processes. Virtual host-level access logging can only use a logger application defined at the virtual host level. Server-level access logging can only use an external logger application defined at the server level. The logger application must be defined in External Apps section first. When this field is specified, the access log will be sent only to the logger application and not the access log file specified in previous entry. Specifies the external application that will receive the access log data sent by LiteSpeed through a pipe on its STDIN stream (file handle is 0). This action can turn debug logging on and off on the fly, and is useful for debugging busy production servers. These settings mean that you will not fill up your hard disk with debug logging, but you will be able to use the Toggle Debug Logging action to control debug output. It's recommended to set Log Level to DEBUG and Debug Level to NONE. Debug logging includes detailed information for each request and response. Active debug logging will severely degrade service performance and potentially saturate disk space in a very short time. Important! Always set this to NONE if you do not need detailed debug logging. Toggle Debug Logging can be used to control debug level on a live server without restarting. ![]() Debug logging is disabled when "Debug Level" is set to NONE even if Log Level is set to DEBUG. Log Level must be set to DEBUG to use this feature. ![]()
0 Comments
Leave a Reply. |