
All distributions supported by the role already collect cron logs. The role won't change the syslog configuration from the default. Implements: blueprint security-rhel7-stig Change-Id: Iea82aa6f2fc81b40d5488a56ee7382b3ef6a2eab
565 B
565 B
---id: RHEL-07-021160 status: exception - manual intervention tag: misc ---
Ubuntu, CentOS and Red Hat Enterprise Linux already capture the logs from cron.
Ubuntu systems collect cron job logs into the main syslog file
(/var/log/syslog
) rather than separate them into their own
log file. CentOS and Red Hat Enterprise Linux systems collect cron logs
in /var/log/cron
.
Deployers should not need to adjust these configurations unless a
specific environment requires it. The tasks in the security role do not
make changes to the rsyslog
configuration.