[PATCH v7 1/4] Add system-wide tunables: ldconfig part

[DJ Delorie]

Florian Weimer <fweimer@redhat.com> writes:
>> Adds support for reading /etc/tunables.conf
>
> Shouldn't this go into /etc/glibc?

I don't think so.  We have /etc/ld.so.conf and thus /etc/tunables.conf.
None of my machines even have an /etc/glibc so I wouldn't expect
sysadmins to "know" to look there (i.e. it's less "discoverable").  I
know *I* hate it when config files are scattered all over my filesystem.

>> that controls overridability by the GLIBC_TUNABLES env var:
>>
>> !glibc.foo=0
>>    ^ May be made more secure
>> +glibc.foo=0
>>    ^ May be overridden
>> -glibc.foo=0
>>    ^ May not be overridden
>
> Can we please use keywords, like in the existing ld.so.conf file?
> We still have "include".  We used to have "hwcap".

I added keyword support but there aren't any good SHORT keywords for
"overridable" and "nonoverridable" so I used those.

> I'm also not convinced that having a separate file hard-coded into
> ldconfig is a good idea.  People will to teach their management tools
> about it (where they currently handle /etc/ld.so.conf.d).  It's also
> not really compatible with this request:

If distros want to add their policies on how they want to organize this
data and manage installs/uninstalls, they can ship a file in /etc with
that policy in it.  Our job is to provide a mechanism, not a policy.