ppc-users@lists.sourceforge.net>
*Subject:* Re: [BackupPC-users] BackupPC_Admin cannot write to LOCK
Ahh, I didn’t install from an RPM. We install from the official tar files
as BackupPC packaging has been spotty in the past, and based on your
SELinux issues, continues to be spotty.
Ahh, I didn’t install from an RPM. We install from the official tar files as
BackupPC packaging has been spotty in the past, and based on your SELinux
issues, continues to be spotty.
> On Aug 28, 2019, at 14:12, Jamie Burchell wrote:
>
> Ah, perhaps its due to which package I have. I’m o
, 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 cont
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 wrote:
>
> Thanks fo
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(/.*)?
Our setup is a little different that yours, but this is the SELinux module I
deploy to my BackupPC server with these steps:
semodule -r backuppc
checkmodule -M -m -o /tmp/backuppc.mod /tmp/backuppc.te
semodule_package -o /tmp/backuppc.pp -m /tmp/backuppc.mod
semodule -i /tmp/backuppc.pp
We also
