First, ProtectSystem=strict will make the entire file system hierarchy (except
/dev, /proc/ and /sys) read-only, so separate ReadOnlyPaths= is not necessary.
Second, ProtectHome=tmpfs will not just mount an empty tmpfs on /root, but also
on /home and /run/user. As it's likely quite common to want to backup /home,
this seems like a footgun.
Finally, it's quite likely that borgbackup will want access to root's SSH keys
in order to connect to remote backup servers.
Note that all these options are commented out by default, so this is more of
a documentation change than any real change in functionality.
When backing up a machine with a monitor using logind to control idle
timeout and things like DPMS, borgmatic can block the screen from
turning on/off with systemd-inhibit. This is because by default
systemd-inhibit will block "idle:sleep:shutdown". Borgmatic does not
need to care about idle, only about suspend and shutdown. So, add an
explicit `--what` flag for what borgmatic should inhibit.
For more information see systemd-inhibit(1).
This commit changes the comment in sample systemd service.
Using a combination of 'ProtectHome' and 'BindPaths' it's possible to
hide the irrelevant paths inside /root from borgmatic service when it is
run.
ReadWritePaths are suggested to be used only for paths that contain borg
repositories and the backup sources can be specified as ReadOnlyPaths.
continuous-integration/drone/pr Build is failingDetails
As borgmatic will log to syslog in the sample crontab/systemd service
files, this makes console output redundant. (cron will mail any console
output to the root user; systemd will log any console output to syslog.)
This adds --verbosity -1 to both files to reduce console output to the
minimum.
David Härdeman
Soumik Dutta
Dan Helfman
Jeffery To
Matthias