Error setting allow_execmod (Was: other problems after selinux-policy-targeted-1.17.30-3.2)
Daniel J Walsh
dwalsh at redhat.com
Wed Jun 15 15:44:46 UTC 2005
Davide Bolcioni wrote:
> Markus Ralser wrote:
>
>> an old error seems to reappear after uptdate to
>> selinux-policy-targeted-1.17.30-3.2.
>
>
> I just updated to selinux-policy-targeted-1.17.30-3.2 and tried
>
> setsebool -P allow_execmod=true
>
> but I get
>
> Error setting boolean allow_execmod to value 1 (No such file or
> directory)
>
> Is a reboot required ? I have other FC3 hosts where the setsebool
> proved unnecessary, as
>
> getsebool allow_execmod
>
> returned "active", although the same RPM is installed. What's up ?
>
> Thank you for your consideration,
> Davide Bolcioni
> --
> There is no place like /home.
>
> --
> fedora-selinux-list mailing list
> fedora-selinux-list at redhat.com
> http://www.redhat.com/mailman/listinfo/fedora-selinux-list
olicy update is on the way.
For now try
setsebool -P allow_execmod=1
chcon -t shlib_t SHAREDLIBARY
You can get an updated policy from
ftp://people.redhat.com/dwalsh/SELinux/FC3
or update to the testers version or
wait till tomorrows updates.
--
More information about the selinux
mailing list