logmgr
In the [logmgr] section, the tokens control the behavior of the logging facility.
capamsc141
In the [logmgr] section, the tokens control the behavior of the logging facility.
- audit_backSpecifies the name of the audit log backup file. OnlyPrivileged Access Managercan write to this file. Users can have READ access only to this file.Default:ACInstallDir/log/seos.audit.bak
- audit_groupSpecifies the group that can read the audit logs. If you set this token tonone, only root can read the audit logs.Privileged Access Managerdoes not verify the value of this token. If you enter an invalid group name, the product does not assign any group permissions to the audit log files.To change the group ownership of an existing audit log file, complete the following steps:Use the selang command chgrp to set the group ownership of the files.Change the UNIX permissions by entering the following command:chmod 640 ACInstallDir/log/seos.auditDefault:none
- audit_logSpecifies the name of the audit log file. When this file reaches the size that is specified inaudit_size,Privileged Access Managerdoes the following actions:
- Closes the file
- Renames it with the name inaudit_back
- Creates an audit log. OnlyPrivileged Access Managercan write to this file. Users can have READ access only to this file.Default:ACInstallDir/log/seos.audit
- audit_max_filesDefines the maximal number of audit log backup files accumulates when it performs date-triggered backups. When the BackUp_Date configuration setting is set to anything other thannone, continuously accumulates date-triggered backup files. This configuration setting lets you reduce disk space uses for audit log backups. When the number of audit log backup files reaches the limit that you set,Privileged Access Managerdeletes the oldest backup file when it creates the newest.Values:
- 0keep all audit log backup files.
- na positive integer greater than zero.
Note:You cannot remove redundant audit log backup files manually becausePrivileged Access Managerprotects these files automatically. Also, if the audit reporting is enabled,Privileged Access Managerdoes not delete a backup file until the Report Agent finishes processing it.Default:0 - audit_sizeSpecifies the maximum size, in KB, of the audit log file.Minimum value: 50 KBDefault:10240stops writing audit records to the audit file when the audit file size exceeds 2 GB.
- BackUp_DateSpecifies the criterion by whichPrivileged Access Managerbacks up the audit log file, and if it adds a timestamp to the backup file name.alwaysbacks up the audit log file when it reaches the size specified in the audit_size configuration setting.Values:none, yes, daily, weekly, monthly
- yes: backs up the audit log file when it reaches the size that is specified in audit_size and adds a timestamp to the backup file name.
- none: backs up the audit log file when it reaches the size that is specified in audit_size and does not add a timestamp to the backup file name.
- daily, weekly, monthly: backs up the audit log file whenever the specified interval has elapsedandwhen it reaches the size that is specified in audit_size, and adds a timestamp to the backup file name. However, if no audit events are written to the audit log file in the specified interval,Privileged Access Managerdoes not back up the file after the interval elapses.Note:counts the specified interval from the time that it creates the first audit log file, and backs up the file at midnight on the appropriate day.
Example:The configuration setting has a value of weekly andPrivileged Access Managercreates the audit log file at 9:00 a.m. Friday 1 April. Many audit events occur this week and the audit log file exceeds the audit_size configuration setting on Monday 4 April.Privileged Access Managerbacks up the audit log file on 4 April and adds a timestamp to the backup file name. A week after the audit log file was first created, at midnight Friday 8 April, the product again backs up the audit log file and adds a timestamp to the backup file name.Default:NONE - error_backSpecifies the name of the error log backup file.Default:ACInstallDir/log/seos.error.bak
- error_groupSpecifies the group that can read the error log files. If you set this token tonone, only root can read the error log files. The product does not verify the value of this token. If you enter an invalid group name, the product does not assign any group permissions to the error log files.To change the group ownership of an existing error log file, complete the following steps:Use the selang command chgrp to set the group ownership of the files.Change the UNIX permissions by entering the following command:chmod 640 ACInstallDir/log/seos.auditDefault:none
- error_logSpecifies the name of the error log file. When this file reaches the size that is specified inerror_size,Privileged Access Managerdoes the following actions:
- Closes the file
- Renames it with the name inerror_back
- Creates an error log. OnlyPrivileged Access Managercan write to this file.Default:ACInstallDir/log/seos.error
- error_sizeDefines the maximum size, in KB, of the error log file.Limits:A minimum value of 50 KB.Default:50
- irecorder_auditSpecifies whether the IR API library routes audit events of existing PMDs in addition to the local security daemon audit events.all - routes audit events of Policy Models in addition to the local security daemon audit events.localhost - routes audit events of the local security daemon only.Default:all
- logconnectedPrevents TCP-CONNECTED records from being written to the audit log.Set logconnected to No to use this feature.Default:no