>I tried running these commands to leave SELinux on in order to get
>backups
>working properly:
>semanage fcontext -a -t bacula_var_run_t '/backup/tapes(/.*)?'
>restorecon -R -v /backup/tapes
>However that made no difference. Still can't write to the directory
>after
>running those commands.
Hi
On Monday 2016-11-07 08:27:46 Josh Fisher wrote:
> On 11/7/2016 7:51 AM, Kern Sibbald wrote:
> > Hello,
> >
> > Selinux is always an administrative problem as several people have
> > already noted. If you really want to use Selinux, you might look at
> > the RedHat (CentOS) distribution. Since
On 11/7/2016 7:51 AM, Kern Sibbald wrote:
Hello,
Selinux is always an administrative problem as several people have
already noted. If you really want to use Selinux, you might look at
the RedHat (CentOS) distribution. Since they support Bacula, I am
pretty sure that they provide all the ne
Hello,
Selinux is always an administrative problem as several people have
already noted. If you really want to use Selinux, you might look
at the RedHat (CentOS) distribution. Since they support Bacula, I
am pretty sure that they provide all the necessary
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tim Dunphy kirjoitti 7.11.2016 4:45:
> hey guys,
>
> Running into an issue with SELinux on my bacula server.
>
> With selinux turned on, I can't write to the backup directory.
>
> This is what I get when I try:
>
> [root@ops:~] #getenforce
> Enfor
On Sunday 2016-11-06 21:45:00 Tim Dunphy wrote:
> hey guys,
>
> Running into an issue with SELinux on my bacula server.
>
> With selinux turned on, I can't write to the backup directory.
>
> This is what I get when I try:
>
> [root@ops:~] #getenforce
> Enforcing
>
> Connecting to Storage daemo
hey guys,
Running into an issue with SELinux on my bacula server.
With selinux turned on, I can't write to the backup directory.
This is what I get when I try:
[root@ops:~] #getenforce
Enforcing
Connecting to Storage daemon File at ops.example.com:9103 ...
Sending label command for Volume "jf-
