On 18 July 2016 at 18:26, Jakub Hrozek wrote:
> On Mon, Jul 18, 2016 at 09:33:35AM +1000, Lachlan Musicman wrote:
> > Ok, I've just spoken with my colleague that has been involved in the IPA
> > roll out, and he said he thought that override_space wasn't compatible
> with
> >
On Mon, Jul 18, 2016 at 09:33:35AM +1000, Lachlan Musicman wrote:
> Ok, I've just spoken with my colleague that has been involved in the IPA
> roll out, and he said he thought that override_space wasn't compatible with
> ID overrides?
I haven't tested that to be honest. But just using my
Ok, I've just spoken with my colleague that has been involved in the IPA
roll out, and he said he thought that override_space wasn't compatible with
ID overrides?
Either way, since we have a working system we are reticent to make too many
changes - soon we will have a test system in place and I
Wont be able to check until Monday morning (Australia's weekend has
started) but can check, yes.
And the reason I reported to you is because you will have more weight with
selinux bug tickets than I would.
cheers
L.
--
The most dangerous phrase in the language is, "We've always done it this
On (15/07/16 12:56), Lachlan Musicman wrote:
>This line:
>
>We have SELinux disabled on all of our servers, but we hadn't disabled this
>check in sssd.conf. So we enabled it in sssd.conf and everything worked
>fine.
>
>Should read that we *disabled* selinux.
>
>selinux_provider = none
Could you
This line:
We have SELinux disabled on all of our servers, but we hadn't disabled this
check in sssd.conf. So we enabled it in sssd.conf and everything worked
fine.
Should read that we *disabled* selinux.
selinux_provider = none
Cheers
L.
--
The most dangerous phrase in the language is,