Admiral Beotch wrote: > I fixed my SELinux problem by changing the context of the mounted > partition that holds TOPDIR... I can't say for certain that I got the > context 100% accurate, but it seems to be a secure choice given how > the httpd process is trying to interact with that part of the file > system. The command that fixed everything was: > > chcon -R -t httpd_log_t /<backup drive mount point>/
httpd_sys_content_t might be a more secure choice, as SELinux might give Apache permissions to write httpd_log_t. But I'm pretty rusty on the details. Also, explicitly setting the context is fine for a temporary solution, but if "restorecon" is ever run, the changes you made might not stick. > > Now I am about to see all my host logs and browse their backups while > keeping selinux enabled. About, or able? > > I hope this helps someone else experiencing the same problem. Indeed. In any case, http://docs.fedoraproject.org/selinux-apache-fc3/ is a good read for securing Apache with SELinux. > > Admiral Beotch Chris ------------------------------------------------------------------------------ _______________________________________________ BackupPC-users mailing list [email protected] List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
