On September 19, 2012 15:27:43 Dmitry Makovey wrote:
On September 19, 2012 15:20:17 Dmitry Makovey wrote:
> Daniel, you saved my day - I thought that something like that should
> exist
> but I completely ommited sepgsql* set as I was under impression that it
> applied to a completely different functionality. I'll use that instead of
> my module. Thank you very much.
spoke too soon:
# setsebool sepgsql_enable_pitr_implementation On
Could not change active booleans: Invalid boolean
so it sounds like it doesn't exist in RHEL? yet?
ok as per
https://bugzilla.redhat.com/show_bug.cgi?id=858406 , Miroslav just
added it, so it definitely doesn't exist yet. But it sounds like it is on it's
way.. thank you Dan and Dominick for the help. I'll stick with my module for
now.
What's the best way of tracking whether above changes made it into RHEL6
policies? Just the changelog?
--
Dmitry Makovey
Web Systems Administrator
Athabasca University
(780) 675-6245
---
Confidence is what you have before you understand the problem
Woody Allen
When in trouble when in doubt run in circles scream and shout
http://www.wordwizard.com/phpbb3/viewtopic.php?f=16&t=19330
--
This communication is intended for the use of the recipient to whom it
is addressed, and may contain confidential, personal, and or privileged
information. Please contact us immediately if you are not the intended
recipient of this communication, and do not copy, distribute, or take
action relying on it. Any communications received in error, or
subsequent reply, should be deleted or destroyed.
---