Which approach configures log rotation to run daily and keep 14 rotated logs?

• A. Create a /etc/logrotate.d/<name> with daily and rotate 14; then run logrotate -f /etc/logrotate.conf to test or apply
• B. Edit /etc/logrotate.conf to set daily and rotate 14 and run logrotate
• C. Use logrotate -d to simulate daily rotation
• D. Use crontab to run logrotate daily

Answer: (A)

Log rotation is driven by a main configuration that includes per-log rules. The preferred approach is to put a dedicated rule for the specific log under /etc/logrotate.d, where you set daily to rotate each day and rotate 14 to keep the latest 14 rotated backups. Since /etc/logrotate.conf includes the files in /etc/logrotate.d, adding your own file automatically becomes part of the overall rotation policy. Running logrotate with the main configuration, for example logrotate -f /etc/logrotate.conf, applies the rules immediately (the -f flag forces rotation, which is useful for testing or applying right away). This modular method is better than editing the central file because it keeps policies isolated and easier to manage. Using -d would only simulate rotation, not perform it, and relying on a separate crontab entry to run logrotate daily bypasses the built-in, centralized scheduling and configuration mechanism.