log-rotate

OVERRIDES runtime profile: uses direct_python (plain Python, no model) because the script is a stdlib-only file rotator — it never invokes the claude CLI or any LLM API, so the scheduler must not inject a provider env.

Daily gzip rotation of oversized workspace logs. Copytruncate semantics: the live file is gzip-copied to <name>.log.1.gz and then os.truncate()d in place, so long-running writers (scheduler systemd unit, tmux pipe-pane, cron >> redirects — all O_APPEND, verified via /proc fdinfo) keep writing into the truncated file without restart. Retention: .1.gz (newest) through .4.gz (oldest); the oldest archive is dropped on each rotation.

Manual run / dry-run:

python3 ~/workspace/scripts/rotate_logs.py --dry-run
python3 ~/workspace/scripts/rotate_logs.py --size-mb 20 --keep 4

Task Definition

tasks/log-rotate.md

Run Asscript

Commandset

Tool-lessNo

BackgroundNo

Runtime profile

Notify destination

python3 ~/workspace/scripts/rotate_logs.py

---
id: log-rotate
name: Rotate oversized workspace logs (copytruncate, keep 4)
schedule: "40 4 * * *"
timeout: 300
retry: false
enabled: true
criticality: medium
run_as: script
command: python3 ~/workspace/scripts/rotate_logs.py
description: Daily copytruncate rotation for ~/workspace/logs (MC-4942 U11 item 16). No sudo / no logrotate on this box, so a pure-python rotator gzips every top-level logs/*.log over 20MB to <name>.log.1.gz (keeping 4 archives) and truncates the live file in place. Safe for the O_APPEND writers that own these logs (systemd append:, shell >>); files modified in the last 5s are skipped (a 60s guard would permanently exempt scheduler.log, which the tick touches every minute).
runtime_profile: direct_python
notify_on: failure
notify_to: elmar
tags: [infrastructure, logs, cleanup]
---

**OVERRIDES runtime profile:** uses `direct_python` (plain Python, no model)
because the script is a stdlib-only file rotator — it never invokes the
`claude` CLI or any LLM API, so the scheduler must not inject a provider env.

Daily gzip rotation of oversized workspace logs. Copytruncate semantics: the
live file is gzip-copied to `<name>.log.1.gz` and then `os.truncate()`d in
place, so long-running writers (scheduler systemd unit, tmux pipe-pane, cron
`>>` redirects — all O_APPEND, verified via /proc fdinfo) keep writing into
the truncated file without restart. Retention: `.1.gz` (newest) through
`.4.gz` (oldest); the oldest archive is dropped on each rotation.

Manual run / dry-run:

```bash
python3 ~/workspace/scripts/rotate_logs.py --dry-run
python3 ~/workspace/scripts/rotate_logs.py --size-mb 20 --keep 4
```

Run History (3)

Started	Finished	Status	Duration	Output	Log
1h ago	1h ago	completed	0s	nothing to rotate in /home/lucienne/workspace/logs (threshold 20MB, keep 4)	View log
1d ago	1d ago	completed	0s	nothing to rotate in /home/lucienne/workspace/logs (threshold 20MB, keep 4)	View log
2d ago	2d ago	completed	3s	rotated persistent-luci.tmux.log (68.4MB) -> persistent-luci.tmux.log.1.gz (5.3MB), truncated in place	View log

Task Definition

Edit Schedule

Run History (3)

Comments (0)

What is Mission Control?