Re: [RFC] [PATCH] libsemanage: Skip policy module re-link when only setting booleans.

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

 



Would be nice to have a global system setting regarding whether saving disk space is a priority. Then this could be one of many things that could work differently depending on whether the sysadmin wants to save space.

On 26 July 2014 5:45:49 AM AEST, Joshua Brindle <brindle@xxxxxxxxxxxxxxxxx> wrote:
>Stephen Smalley wrote:
>> Motivated by:
>> https://bugzilla.redhat.com/show_bug.cgi?id=1098446
>>
>> I believe this is always safe for booleans because we only set their
>> value; we are never adding new ones via semanage, unlike for example
>> users, ports, nodes, and interfaces.  For the rest, I was wondering
>why
>> we don't save the linked file and just reuse it on those changes
>rather
>> than re-linking each time - that seems like it would be
>straightforward
>
>We originally kept the linked copy around and had intended to do what 
>you are saying above but removed it when the minimal Red Hat guys 
>complained about the size of it.
>
>> to do in libsemanage and make those operations significantly faster
>and
>> less memory intensive.
>
>_______________________________________________
>Selinux mailing list
>Selinux@xxxxxxxxxxxxx
>To unsubscribe, send email to Selinux-leave@xxxxxxxxxxxxx.
>To get help, send an email containing "help" to
>Selinux-request@xxxxxxxxxxxxx.

-- 
Sent from my Samsung Galaxy Note 2 with K-9 Mail.

_______________________________________________
Selinux mailing list
Selinux@xxxxxxxxxxxxx
To unsubscribe, send email to Selinux-leave@xxxxxxxxxxxxx.
To get help, send an email containing "help" to Selinux-request@xxxxxxxxxxxxx.




[Index of Archives]     [Selinux Refpolicy]     [Linux SGX]     [Fedora Users]     [Fedora Desktop]     [Yosemite Photos]     [Yosemite Camping]     [Yosemite Campsites]     [KDE Users]     [Gnome Users]

  Powered by Linux