ionice not getting applied when running through cron?
Opened this issue · 0 comments
W1zzardTPU commented
Looks like restic doesn't get ionice'd properly
Using supercronic as documented in "User schedule in container"
root@backup-storage-5647559f4c-x8l49:/# ps -ax
PID TTY STAT TIME COMMAND
1 ? SNs 0:00 /bin/sh -c resticprofile schedule --all && supercronic -passthrough-logs /etc/crontab
30 ? SNl 0:00 supercronic -passthrough-logs /etc/crontab
38 ? SN 0:00 /bin/sh -c cd / && /usr/bin/resticprofile --no-ansi --config /etc/resticprofile/profiles.yaml run-schedule backup@default
39 ? SNl 0:00 /usr/bin/resticprofile --no-ansi --config /etc/resticprofile/profiles.yaml run-schedule backup@default
75 ? SNl 47:42 /usr/bin/restic backup --exclude=<redacted> --host=<redacted> --one-file-system --password-file=/etc/resticp
385 pts/0 Ss 0:00 bash
423 pts/0 R+ 0:00 ps -ax
root@backup-storage-5647559f4c-x8l49:/# ionice -p 39
best-effort: prio 6
root@backup-storage-5647559f4c-x8l49:/# ionice -p 75
none: prio 0
root@backup-storage-5647559f4c-x8l49:/# resticprofile default.show
2024/07/01 08:22:35 using configuration file: /etc/resticprofile/profiles.yaml
global:
ionice: true
ionice-class: 2
ionice-level: 6
priority: low
...