Information: Forum is in read-only mode
For details and other support options see

[closed] WinSyslog 8.0 (Build 449) RB - Updated 2007-08-01

Support, Questions and Discussions on WinSyslog

Moderator: alorbach

Google Ads

[closed] WinSyslog 8.0 (Build 449) RB - Updated 2007-08-01

Postby alorbach » Mon Feb 05, 2007 3:08 pm


The Rolling Beta program is open, features and bugfixes will be added continuously.
The changelog below helps you to keep track on the changes.
Feel free to test this new rolling beta version, if you are experiencing any problems,
kindly let us know via support email ( or this forum.

A note on Win32 and x64 Edition
WinSyslog is available for 2 platforms. Since Build 448, bot Editions are unified in one Setup file, this includes the win32 platform and the x64 platform. If you had win32 installed before, your installation will be upgraded to x64 automatically without loss of any configurations.

:arrow: Download of the Rolling beta
:arrow: WinSyslog 8.0 Rolling Beta Manual

Below the change since version 7.3:

:!: 2007-08-01 / build 449
:arrow: Features/Enhancements
- Filter Engine: Added new special Filter called "FileExists", this filter kindly checks if a file does exist or not.
- Forward Syslog Action: Added a new major feature into this Action, Diskqueue. This new option is only available for TCP based Syslog. Whenever a connection to a remote syslog server failes, the action starts caching the syslog messages in a local temp file. The folder for these files can be configured. You do not need to worry about multiple Actions using this feature, the filenames are generated using a unique GUID which is automatically generated for each Action. Once the Syslog target becomes available again, the cached messages are being sent automatically. If you restart the Service while the Syslog Cache was active, it cannot be checked during service startup if the Syslog target is available now. Once the action is called again, the check is done and if the syslog target is available, the messages are being sent. The size of this cache is only limited by the disk size. Files are splitted by 10MB by default, but this can also be configured. The maximum supported file size is 2GB.

:!: 2007-07-10 / build 448
:arrow: Features/Enhancements
- Setup: The Win32 and x64 edition are now unified in one installation package! This means ONE Setup, both editions - automatically detected during the installation. So if you install WinSyslog on a Win32 based System, the Win32 Version of the Service will be installed. If you install WinSyslog on a x64 based system, the x64 Version of the service will be installed.

:arrow: Bugfixes
- Syslog Listener: This bug concerns the UDP and TCP listener only. A problem with RFC3164 parsing could lead to an internal crash of the Syslog Listener. This condition happened very
seldom, depending on some syslog messages. This Bug has been fixed now.

:!: 2007-06-05 / build 446
:arrow: Features/Enhancements
- Send Syslog/Setp Action: It is now possible to configure a service name for the port instead of a number only. This service name will be used to make a port lookup in the system services file. This feature was added by a customer request.
- Syslog Listener: Implemented the compressed syslog receiver for syslog over UDP (over TCP is not yet supported).
- Property Engine: Added new property $NOW, which is the local time in the format YYYY-MM-DD HH.MM.SS. Note that "." is used instead of ":" in the timestamp to make this value suitable for filename-generation.
- Property Engine: Added property replacer option "compsp", to compress spaces inside a property
- Core Engine: Enhanced performance of debuglogging and added more debug outputs into certain areas of the WinSyslog Service.
- Core Engine: Implemented advanced memory management which is available on Windows XP/2003 and higher. This will speeds up overall processing in general depending on your Services and Actions.

:arrow: Bugfixes
- Syslog Action: Fixed a bug where a UDP socket send returned with "WSAEMSGSIZE (10040) Message too long" when an oversize packet was tried to be sent. The message is now simply trunscated, there is no other option available to handle such cases.
- Rule Engine: Fixed a bug that could cause the product to become unresponsive after an error in an action.
- Property Engine: Fixed a bug which could leed to invalid detections of search strings.

:!: 2007-02-05 / build 444
:arrow: Features/Enhancements
- Forward Syslog Action: Added support for sending multiple messages over a persistent syslog/TCP connection.
- Forward Syslog Action: Added capability to force -transport-tls like octet-counted framing for syslog/TCP connections
- Syslog Server: Added capability to work with -transport-tls framing on the syslog server side (but not yet compression)

:arrow: Bugfixes
- SendEmail & Forward Syslog Action: Added a Send&Receive Timeout of 30 seconds to avoid that a broken TCP Connections blocks the Action processing.
Site Admin
Posts: 1627
Joined: Thu Feb 13, 2003 11:55 am

Google Ads

Return to WinSyslog

Who is online

Users browsing this forum: No registered users and 0 guests