Log level to use for logging to the Event Log on Windows systems, or the syslog on UNIX systems.
Valid log levels include:
The default value is NONE.
Be careful setting the log level to a value that is too high.
The DEBUG log level, for example will very
quickly fill up your syslog or event log.
In addition, NOTICE or ADVICE
messages exist, but neither will ever be logged to UNIX syslog or Windows Event Log.
Sets the facility code to use when logging to the syslog on UNIX systems.
Sets the identity (or event source on Windows) to use when logging to the syslog.
Ensures whether the event source should exist or not in the Windows registry.
Specifies the local host name included in the packets sent to a remote syslog.
Filters messages sent to the syslog (or event log on Windows) according to their log levels.
Specifies the host name of a remote syslog server where log outputs should be redirected to.
Specifies the port that the remote syslog server is listening on.
Forces messages to be broken up into individual lines making them easier to read.
Displays advice whenever certain common problems are detected.
Controls the log level of messages related to the child process management.
Filters messages sent to the console according to their log levels.
Controls at which log level the generated command line will be logged.
Filters messages of the log dialog according to their log levels.
Filters messages sent to the log file according to their log levels.
Controls at which log level the ping alert messages will be logged.
Controls at which log level the configuration properties will be logged.
Controls at which log level warnings about invalid property values will be logged.
Filters messages included in the emails according to their log levels.
Controls the log level of messages being logged each time a specific event takes place.
Controls the message which will be logged each time a specific event takes place.
Controls the log level of messages related to the event commands being executed.
Sets the path to a file containing commands to be executed.
Enables test commands.
Specifies time intervals to use when testing the existence of command file.
Controls whether or not the Wrapper configuration file will be reloaded in the event of a JVM restart.
Enables the PAUSE and RESUME actions.
Uses the system time (instead of a background timer thread) for all internal timekeeping functions of the Wrapper.
Controls whether the Wrapper uses a dedicated thread to process console output from the JVM.
Copyright (c) 2004-2018, Tanuki Software, Ltd. All Rights Reserved.