Tools
Difference between running Kiwi Syslog Daemon as a service and standard application
This article explains the difference between running the Kiwi Syslog as a service and as a standard application.
First published date
Last published date
Overview
When you run Kiwi Syslog as a service, the service runs in the background. It can be scheduled to start automatically when the server comes up and receives messages whenever it is running. Care must be taken when installing Kiwi Syslog Server as Service. Before installing a new version, you must first ensure that any existing version of the service has been stopped and uninstalled.
Product section
Resolution
The Standard (Non-Service) application runs on Windows 8, Windows 8.1, Windows 10, Windows Server 2012 and 2012 R2, Windows Server 2016.
*Note: On a 64-bit system, Kiwi Syslog Server runs in Windows-on-Windows 64-bit (WOW64) mode. WOW64 is a subsystem of the Windows operating system that is capable of running 32-bit applications. WOW64 is included on all Windows 64-bit versions. The maximum amount of RAM Kiwi Syslog Server can consume is 1.6 GB.
When you install Kiwi Syslog Daemon as a Service, it is made up of two parts: the Service Manager and the Service.
Service Manager
The Service Manager is an interactive GUI application that controls the state of the Service (Stop, Start, Install, Uninstall). It is run by a user when they log in to the system to check on the service status. It handles the audible alarms and the visual display of syslog messages that have been received and processed by the service. Using the File > Setup menu, the user can setup the properties of the service and define Rules that contain specific Filters and Actions for the service to act on.
Service
The Service is a non-interactive process (no GUI), that receives and processes the incoming syslog messages. It is run automatically at system startup time without need for a user to be logged in. The Kiwi Syslog Daemon Service is controlled by the Service Manager.