get_running_backups() (napalm-device-types 4.34.0, RunningBackupsMixin) through LinuxProcessReadingsMixin, so OpenMediaVault and QNAP inherit it.
One round trip as the login user: the clock, ps -eo pid=,etimes=,args= and each process's cgroup. A process of restic, resticprofile, autorestic, borg, borgmatic, duplicity, duply, rsnapshot, rdiff-backup, proxmox-backup-client, kopia or btrbk doing a backup, prune, check or copy counts (not a mount, restore or listing); borg serve counts as the receiving end of another host's backup.
Its job is the systemd service it runs in (the timer's service); none for cron or a login session.
A ps without etimes (busybox) fails the reading instead of reporting nothing.
tests/test_running_backups.py (36), full suite 402 passed, ruff, napalm-standard check and ratchet locally; the command run on a real Linux host.
Depends on
NAPALM/napalm-device-types#102 (4.34.0, RunningBackupsMixin). CI installs napalm-device-types from PyPI, so the install jobs fail until 4.34.0 is tagged and published there; rerun them then.
## Summary
- `get_running_backups()` (napalm-device-types 4.34.0, `RunningBackupsMixin`) through `LinuxProcessReadingsMixin`, so OpenMediaVault and QNAP inherit it.
- One round trip as the login user: the clock, `ps -eo pid=,etimes=,args=` and each process's cgroup. A process of restic, resticprofile, autorestic, borg, borgmatic, duplicity, duply, rsnapshot, rdiff-backup, proxmox-backup-client, kopia or btrbk doing a backup, prune, check or copy counts (not a mount, restore or listing); `borg serve` counts as the receiving end of another host's backup.
- Its job is the systemd service it runs in (the timer's service); none for cron or a login session.
- A `ps` without `etimes` (busybox) fails the reading instead of reporting nothing.
## Related Issue
NetOrk/netork#2318
## Testing
- `tests/test_running_backups.py` (36), full suite 402 passed, ruff, `napalm-standard check` and `ratchet` locally; the command run on a real Linux host.
## Depends on
NAPALM/napalm-device-types#102 (4.34.0, `RunningBackupsMixin`). CI installs napalm-device-types from PyPI, so the install jobs fail until 4.34.0 is tagged and published there; rerun them then.
netOrk holds a host's restart after patching while a backup runs on it
(NetOrk/netork#2318) and asks right before the restart. On a Linux host a
file-level backup is a process of a backup tool, started by a timer, a cron
line or by hand, so get_running_backups() (napalm-device-types 4.34.0) reads
the processes, the clock and each process's cgroup in one round trip as the
login user. What a tool does comes from its subcommand: restic backup is a
backup, restic forget a prune, restic mount none; borg serve counts, as the
receiving end of another host's backup. The systemd service a backup runs
in is its job, the timer's service netOrk shows as its scheduled job.
A ps without etimes (busybox) fails the reading rather than report nothing.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
get_running_backups()(napalm-device-types 4.34.0,RunningBackupsMixin) throughLinuxProcessReadingsMixin, so OpenMediaVault and QNAP inherit it.ps -eo pid=,etimes=,args=and each process's cgroup. A process of restic, resticprofile, autorestic, borg, borgmatic, duplicity, duply, rsnapshot, rdiff-backup, proxmox-backup-client, kopia or btrbk doing a backup, prune, check or copy counts (not a mount, restore or listing);borg servecounts as the receiving end of another host's backup.pswithoutetimes(busybox) fails the reading instead of reporting nothing.Related Issue
NetOrk/netork#2318
Testing
tests/test_running_backups.py(36), full suite 402 passed, ruff,napalm-standard checkandratchetlocally; the command run on a real Linux host.Depends on
NAPALM/napalm-device-types#102 (4.34.0,
RunningBackupsMixin). CI installs napalm-device-types from PyPI, so the install jobs fail until 4.34.0 is tagged and published there; rerun them then.