From Boldcore's wiki
(Created page with "Usually, we just disable SELinux, instead of configuring it --lazy way :D <br> I think, that enabling application using the following commands is better approach. <pre> ause...") |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
Usually, we just disable SELinux, instead of configuring it --lazy way :D <br> | Usually, we just disable SELinux, instead of configuring it --lazy way :D <br> | ||
| − | I think, that enabling application using the following commands is better approach. | + | I think, that enabling application using the following commands is a bit better approach. |
<pre> | <pre> | ||
| − | ausearch -c " | + | ausearch -c "your_application_name" | audit2alllow -M enable-app |
semodule -i enable-app.pp | semodule -i enable-app.pp | ||
</pre> | </pre> | ||
Then restart the service and it should work with no issues. | Then restart the service and it should work with no issues. | ||
Latest revision as of 02:32, 15 May 2018
Usually, we just disable SELinux, instead of configuring it --lazy way :D
I think, that enabling application using the following commands is a bit better approach.
ausearch -c "your_application_name" | audit2alllow -M enable-app semodule -i enable-app.pp
Then restart the service and it should work with no issues.