Compatibility :	3.5.24
Editions :
Platforms :

Some log messages that the Wrapper generates contain multiple lines. These are transparently logged as individual lines in the console, log file and other targets. But with the Windows Event Log and UNIX syslog, the messages are intentionally kept as a single message to make them easier to read. In some cases however, you may wish to force these messages to be broken up into individual lines.

wrapper.syslog.split_messages=TRUE

• wrapper.syslog.facility (3.2.1)

  Sets the facility code to use when logging to the syslog on UNIX systems.

• wrapper.syslog.ident (3.2.0)

  Sets the identity (or event source on Windows) to use when logging to the syslog.

• wrapper.syslog.ident.enable (3.5.28)

  Ensures whether the event source should exist or not in the Windows registry.

• wrapper.syslog.local.host (3.5.0) ( Std/Pro )

  Specifies the local host name included in the packets sent to a remote syslog.

• wrapper.syslog.loglevel (2.2.5)

  Filters messages sent to the syslog (or event log on Windows) according to their log levels.

• wrapper.syslog.remote.host (3.5.0) ( Std/Pro )

  Specifies the host name of a remote syslog server where log outputs should be redirected to.

• wrapper.syslog.remote.port (3.5.0) ( Std/Pro )

  Specifies the port that the remote syslog server is listening on.

• wrapper.syslog.split_messages (3.5.24)

  Forces messages to be broken up into individual lines making them easier to read.