4.3. Logging Settings

These settings control how Hyper writes it's activity logs.

Note

These setting controls the activity log of Hyper and not a transactional write-ahead log.

4.3.1. log_config

Can be used to disable Hyper's logging by setting it to the empty string. By default, logging is enabled.

4.3.2. log_dir

Specifies the directory into which Hyper's log files will be written.

4.3.3. log_file_max_count

Specifies how many Hyper log files are kept until the oldest ones are deleted. This setting only has an effect if multiple log files will be created (see: log_file_size_limit). For example, if log_file_max_count is set to 2 and log_file_size_limit is set to 100M, there will be at most two log files with a file size of up to 100 MB containing the most recent log information.

It is not recommended to set the limit to 1, since this can lead to situations in which very little log information is available. This is because the old log file will be deleted immediately when a new log file is started.

When set to 0, the number of log files is not limited.

Default value: 0

4.3.4. log_file_size_limit

Specifies how large a Hyper log file is allowed to grow before logging switches to a new log file. When this setting is set to a value greater than zero, the log files will be suffixed with a timestamp indicating the time at which the logging into this file started. The setting's value can be specified in K(KB), M(MB), G(GB) or T(TB) units. For example, you can specify 100M to limit the file size of each log file to 100 MB. A limit on how many log files should be kept around can be specified with log_file_max_count.

When set to 0, the log file size is not limited and no timestamps are added to the log file name.

Default value: 0