This documentation is for legacy Kiwi Syslog Server versions 9.8.2 and older.
Use this Kiwi Syslog Server registry setting to enable syslogd to modify its priority setting in Windows.
|Section (32-bit Windows OS)||HKEY_LOCAL_MACHINE\SOFTWARE\SolarWinds\Syslogd\Properties|
|Section (64-bit Windows OS)||HKEY_LOCAL_MACHINE\Software\WOW6432Node\SolarWinds\Syslogd\Properties|
|Type||Syslog Process Priority|
Acceptable values are listed below.
|0||Low||Specify this class for a process whose threads run only when the system is idle. The threads of the process are preempted by the threads of any process running in a higher priority class. An example is a screen saver. The idle-priority class is inherited by child processes.|
|1||Below Normal||Indicates a process that has priority above Idle but below Normal.|
|2||Normal||(Default value.) Specify this class for a process with no special scheduling needs.|
|3||Above Normal||Indicates a process that has priority above Normal but below High.|
|4||High||Specify this class for a process that performs time-critical tasks that must be executed immediately. The threads of the process preempt the threads of normal or idle priority class processes. An example is the Task List, which must respond quickly when called by the user, regardless of the load on the operating system. Use extreme care when using the high-priority class, because a high-priority class application can use nearly all available CPU time.|
Specify this class for a process that has the highest possible priority. The threads of the process preempt the threads of all other processes, including operating system processes performing important tasks. For example, a real-time process that executes for more than a very brief interval can cause disk caches not to flush or cause the mouse to be unresponsive.
Realtime priority can cause system lockups.