On Sat, May 30, 2026 at 01:06:36PM -0400, [email protected] wrote: > I've done a lot of digging into this, and while I have not solved it yet, I > want to document in case anyone else runs into this problem and finds this > through archives of this mailing list. > > First off, this is an issue introduced with the recently released Ubuntu > 26.04 LTS. I fired up a spare machine that had 24.04 LTS running on it, and > all I had to do was "sudo apt install apache2" and "sudo apt install > backuppc", start both with systemctl and was instantly up and running, with > no problems modifying the configuration files. If I don't get this figured > out I may just go and load 24.04 on my backuppc server box, but would prefer > to be more up to date.
[...]
This is (almost certainly by now) a new "hardening" feature of
systemd, which mounts (-bind, I think) some things (but only for
some daemons!), among others /usr, /boot, /efi and, depending on
config, /etc read-only.
This explains nicely the -EROFS you are getting. It is not a lie.
Quoting from [1]:
From the documentation on ProtectSystem=
Takes a boolean argument or the special values "full" or
"strict". If true, mounts the /usr and the boot loader
directories (/boot and /efi) read-only for processes
invoked by this unit. If set to "full", the /etc directory
is mounted read-only, too.
So systemd trying to be helpful, it seems.
Cheers
[1]
https://askubuntu.com/questions/1275668/logrotate-succeeds-when-manually-run-as-root-but-fails-with-read-only-file-sys
--
tomás
signature.asc
Description: PGP signature
_______________________________________________ BackupPC-users mailing list [email protected] List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: https://github.com/backuppc/backuppc/wiki Project: https://backuppc.github.io/backuppc/
