You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add support for "exec" action in max_log_file_action
See issue #220
auditd now accepts an exec action for max_log_file_action. When triggered,
the daemon suspends logging, executes the configured program, and resumes
logging automatically once the process exits. A new configuration field
max_log_file_exe records the script to run. The daemon tracks the child
PID and handles SIGCHLD to resume logging.
- Documented the new “exec” option for max_log_file_action with usage details
- Added the SZ_EXEC enum and the max_log_file_exe path in the configuration
structure
- Implemented execution handling and resuming logic in check_log_file_size
- Exposed helper functions for child PID tracking
- Updated child_handler in auditd to resume logging when the exec child exits
/path-to-script will execute the script. You cannot pass parameters to the script. The script is also responsible for telling the auditd daemon to resume logging once its completed its action. This can be done by adding
121
+
.Iauditdctl--signalresume
122
+
to the script. Also note that logging is stpped which this script runs. Whatever it does needs to be real quick because events are backing up in the kernel. The script
123
+
.BMUST
124
+
delete or rename /var/log/audit/audit.log or when logging resumes, it will retrigger executing the script.
119
125
.IR suspend
120
126
will cause the audit daemon to stop writing records to the disk. The daemon will still be alive. The
0 commit comments