This is the mail archive of the
mailing list for the glibc project.
Re: A per-user or per-application ld.so.cache?
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: GNU C Library <libc-alpha at sourceware dot org>
- Date: Tue, 9 Feb 2016 01:04:26 -0500
- Subject: Re: A per-user or per-application ld.so.cache?
- Authentication-results: sourceware.org; auth=none
- References: <56B8E105 dot 8030906 at redhat dot com> <20160209043500 dot GB7732 at vapier dot lan>
On 02/08/2016 11:35 PM, Mike Frysinger wrote:
> On 08 Feb 2016 13:40, Carlos O'Donell wrote:
>> Might it make sense to have a per-user ld.so.cache for
>> this case? Might we even entertain a per-application
> i wouldn't mind adding a new env knob like LD_LIBRARY_CACHE with the
> same characteristics as LD_LIBRARY_PATH such as:
> - it is searched before the system cache
> - it is ignored in set*id environments
I like it. We teach ldconfig to generate cache files, and then
we can even get some cache testing into the testsuite easily
without having to do chroot based testing right away.