... *Back to [[Book|Administrator's Configuration File Reference#cfr]] [[Topic|Administrator's Configuration File Reference#chap4]]*
h2. Settings specified in {{magnus.conf}}
h3. {{ChildRestartCallback}}
The {{ChildRestartCallback}} directive determines whether the Web Server calls the NSAPI functions that were registered using the {{daemon_atrestart}} function.
If you set {{ChildRestartCallback}} to {{on}}, the server calls the registered NSAPI functions when it shuts down or restarts. If you set {{ChildRestartCallback}} to {{off}}, the server never calls the registered NSAPI functions. If you do not explicitly set a value for {{ChildRestartCallback}}, the server calls the registered NSAPI functions when it shuts down or restarts only if all NSAPI Server Application Functions (SAFs) complete request processing before the {{TerminateTimeout}} timeout elapses.
|| Syntax ||
|{{ChildRestartCallback _value_}}
where {{_value_}} is {{on}} or {{off}}. |
h3. {{Init}}
The {{Init}} directives load and initialize server modules and NSAPI plug-ins.
|| Syntax ||
|{code}
Init fn="_function_" _param1_="_value1_" ..._paramN_="_valueN_" |
... h3. {{KernelThreads}}
(Windows only) On Windows, the Web Server supports both kernel-level and user-level threads. User threads are scheduled by Netscape Portable Runtime (NSPR) within the process, whereas kernel threads are scheduled by the host's operating system. Usually, the standard debugger and compiler are intended for use with kernel-level threads.
If you set {{KernelThreads}} to {{1}} ( on ), the server uses the kernel-level threads. If you set {{KernelThreads}} to {{0}} ( off ), the server uses the user-level threads, which might improve performance.
|| Syntax || Default ||
|{{KernelThreads _value_}}
where {{_value_}} is {{0}} or {{1}} | {{0}} ( off ) |
h3. {{NativePoolMaxThreads}}
(Windows only) The {{NativePoolMaxThreads}} directive determines the maximum number of threads in the native (kernel) thread pool.
|| Default ||
| {{0}} |
h3. {{NativePoolMinThreads}}
(Windows only) The {{NativePoolMinThreads}} directive determines the minimum number of threads in the native (kernel) thread pool.
|| Default ||
| {{1}} |
h3. {{NativePoolQueueSize}}
(Windows only) The {{NativePoolQueueSize}} directive determines the number of threads that can wait in a queue for the thread pool. If all threads in the pool are busy, the next request-handling thread that needs to use a thread in the native pool must wait in a queue.
If a queue is full, the next request-handling thread that tries to get in the queue is rejected and the server returns a busy response to the client. The server is then free to handle another incoming request.
|| Default ||
| {{0}} |
h3. {{NativePoolStackSize}}
(Windows only) The {{NativePoolStackSize}} directive determines the stack size of each thread in the native (kernel) thread pool.
|| Default ||
| {{0}} |
h3. {{TerminateTimeout}}
The {{TerminateTimeout}} directive specifies the time (in seconds) that the server waits for NSAPI SAFs to complete the processing of any active requests before it shuts down. Increase the {{TerminateTimeout}} value to allow in-progress HTTP transactions to complete gracefully, or shorten the value to allow the server to shut down more quickly.
|| Syntax || Default ||
|{{TerminateTimeout _value_}}
where {{_value_}} is an interval in seconds. | {{30}} |
h3. {{Umask}}
(UNIX only) The {{Umask}} directive specifies the maximum file permissions granted by NSAPI functions that create files and directories.
|| Syntax || Default ||
|{{Umask _permissions_}}
where {{_permissions_}} is a UNIX file permissions value in octal notation. | {{0777}} | |