Blueforce-Linux/config/systemd/logrotate-blueforce
emirhanmamak-blueforce 503f4df2ae Enhance WireGuard restart playbook with operation wave validation
- Updated `bf-wireguard-restart.yml` to include dynamic host targeting based on `operation_wave`.
- Added pre-tasks to assert that the operation wave is approved and confirmed, ensuring proper execution context.
- Modified the service restart task to use a more structured command format.
- Adjusted `operations.py` and `ui_gui.py` to reflect changes in operation scope from "simple" to "wave" for relevant operations.
- Improved UI handling in `ui_gui.py` and `ui_surfaces.py` for better output management and user interaction.
- Updated log rotation configuration to target specific log files.
- Enhanced systemd service configurations for WireGuard to improve restart behavior.
- Refined firstboot scripts to ensure proper handling of dealer ID and state management.
- Improved error handling and rollback mechanisms in identity and installation scripts.
2026-09-17 17:06:58 +03:00

20 lines
652 B
Text

# Purpose: Rotate MEG and Blueforce application logs to cap disk use.
# Scope: /var/log/blueforce and /var/log/meg file logs; install to /etc/logrotate.d/.
# Safety: Idempotent under logrotate; validate with logrotate -d before deploying.
# Ref: docs/15-LOGGING.md, K-14.
/var/log/blueforce-console.log /var/log/meg/*.log {
weekly
rotate 7
size 10M
maxage 30
compress
delaycompress
missingok
notifempty
create 0640 root adm
sharedscripts
postrotate
/usr/bin/systemctl kill --signal=SIGHUP rsyslog.service >/dev/null 2>&1 || true
endscript
}
# NOTE: install.log and update-history.log stay append-only and are excluded here.