Limiting the size of message logs

By default, message logs grow without limit. Limiting message log size requires the directories and file systems that contain message log files must be checked on a periodic basis to ensure that enough space is available, and to prune the log files or make more space available as necessary.

The routing files can be modified to limit the amount of disk space used for message logs.

Consider the routing specification that is shown in Figure 1.

FATAL:STDOUT:-;UTF8FILE.10.100:/var/PolicyDirector/log/msg__pd
mgrd_fatal_utf8.log:644:ivmgr:ivmgr
ERROR:STDOUT:-;UTF8FILE.10.100:/var/PolicyDirector/log/msg__pd
mgrd__error_utf8.log:644:ivmgr:ivmgr
WARNING:STDOUT:-;UTF8FILE.5.1000:/var/PolicyDirector/log/msg__
pdmgrd_warning_utf8.log:644:ivmgr:ivmgr
NOTICE:STDOUT:-;UTF8FILE.5.1000:/var/PolicyDirector/log/msg__p
dmgrd_notice_utf8.log:644:ivmgr:ivmgr
NOTICE_VERBOSE:STDOUT:-;XMLFILE.10.500:/var/PolicyDirector/log
/msg__pdmgrd_verbose_utf8.xml:644:ivmgr:ivmgr

All message files that are produced by this message log specification are of a determinate size, thus the maximum disk space that can be used by all of the files can be calculated.

Parent topic: Message event logging