You are not logged in.
Pages: 1
I would like to have my hourly backups available in a read-only directory. Currently I have this set up by hiding the backup read-write disk in /root/backup, and it's bind-mounted, read-only, to /backup. That seems too complicated for my tastes. Is there any way to use ACLs to disable write-access for a directory tree while preserving regular permissions, owners, and groups? I've tried, but it always seems that a file's owner can always, e.g., delete it, which is exactly what I don't want. In reading acl (5), that behavior seems to be expected as per step one of the algorithm. Essentially, then, is there a way around that?
Thanks!
Offline
You might consider adding the immutable flag on the file(s) with "chattr +i" That way it cannot be modified or deleted even by root. see man chattr for more information.
Smarter than a speeding bullet
My Goodreads profile
Offline
I had thought about that, but I'm hoping to have it handled by the filesystem on creation, so there's no potential time where a file will be unprotected. Thus my looking into ACLs, where you can have default entries duplicate themselves through the tree.
Offline
Pages: 1