Error setting allow_execmod (Was: other problems after selinux-policy-targeted-1.17.30-3.2)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxx
http://www.redhat.com/mailman/listinfo/fedora-selinux-list

[Index of Archives]     [Fedora Users]     [Fedora Desktop]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Campsites]     [KDE Users]     [Gnome Users]

  Powered by Linux