Ah, perhaps its due to which package I have. I’m on CentOS 7 with the package from hobbes1069-BackupPC which appears to be from the Fedora project.
Kind regards, *Jamie* *From:* Ray Frush [mailto:fr...@rams.colostate.edu] *Sent:* 28 August 2019 21:05 *To:* General list for user discussion, questions and support < backuppc-users@lists.sourceforge.net> *Subject:* Re: [BackupPC-users] BackupPC_Admin cannot write to LOCK So, I’m running on a RedHat 7 flavored box. ’semanage fcontext -l’ returns no items for specific paths for BackupPC on my system. Also my systems have no content in /usr/share/selinux/packages/, which is why I wrote my own. On Aug 28, 2019, at 13:23, Jamie Burchell <ja...@ib3.uk> wrote: Thanks for those details. There does appear to be a policy in place already (/usr/share/selinux/packages/BackupPC/BackupPC.pp) # semanage fcontext -l | grep BackupPC /etc/BackupPC(/.*)? all files system_u:object_r:httpd_sys_rw_content_t:s0 /var/run/BackupPC(/.*)? all files system_u:object_r:var_run_t:s0 /var/log/BackupPC(/.*)? all files system_u:object_r:httpd_log_t:s0 /etc/BackupPC/LOCK all files system_u:object_r:httpd_lock_t:s0 No mention of /var/lib/BackupPC though. Interesting that the LOCK file is mentioned here yet is trying to write it to the data folder?
_______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
