@  #$ Abotu KLog
KLog is our Win32 implementation of *nixsyslog daemon to support remote logging of messages from unix servers, routers, terminal servers and other syslog-enabled devices/applications.

Enjoy!
Copyright (c) 1998-2005 Klever Group (http://www.klever.net/)
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Author: Michael Krelin (hacker@klever.net)
Fan mail send to gefilte@klever.net
#$
1.1.1-trunk - 
• Added vertical resizability
1.1 - July 11th, 2004
• Change of license and opening the source code
• Minor changes in code, mostly bugfixes
#$ Using KLog
When you start KLog for the first time it is set to the configuration in which it will silently catch all incoming messages and display them in the log window. Scroll length in initial configuration is set to 15 lines. To learn how to modify this initial configuration you may want to proceed to the Main Window section.
#$ Main Window
Essentially, main window is a tabbed collection of 'Destinations'. For each destination you can set the destination itself, events criteria and sound KLog will produce when triggered by event matching criteria.
Each tab consists of following fields:
•  Short description - short descriptive text appearing on the tab on top of window.
•  Log to File/Log to Host/Don't Log radio buttons - let you specify where to forward the events matching criteria below.
•  File/Host name - Either file name for logging or host name to forward syslog messages to. (note: host address lookups are performed by blocking call, so if you it takes time to resolve host from it's name Klog  may seem to lock up for a while)
•  IP/mask pairs list - lets you enter ip address/netmask pairs to specify access list for this destination. If none are entered – all hosts activities are logged into selected destination.
•  Facility/priority pattern - may be set in two ways: either by selecting desired facility from the dropdown list and check appropriate priorities and repeat this procedure for every facility or by clicking 'edit logging pattern' button and use the dialog box to edit logging pattern. If you have experience with logging you don't need any explanation about logging facilities/priorities what are they all about and why do you need them. If you don't, then you, probably, don't need KLog.
•  Sound to play when triggered - whenever event is logged using current destination KLog may produce the sound to make you aware of its activity. You can select any preset sound or specify your own wave file.
•  Log window - shows recent activity.
#$ Edit Logging Pattern Dialog
Use this tabbed dialog to edit your logging pattern. Logging facilities are separated into three tabs for your convenience. Use top/left rows of buttons to turn a whole bunch of priorities/facilities, bottom/right rows of buttons to toggle the whole column/row, or simply turn on/off individual facility/priority pairs.