This is the mail archive of the
mailing list for the glibc project.
Re: A per-user or per-application ld.so.cache?
- From: Ben Woodard <woodard at redhat dot com>
- To: "Carlos O'Donell" <carlos at redhat dot com>
- Cc: Florian Weimer <fweimer at redhat dot com>, libc-alpha at sourceware dot org
- Date: Mon, 8 Feb 2016 15:00:26 -0800
- 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> <56B8E810 dot 1040609 at redhat dot com> <56B8F860 dot 6060707 at redhat dot com> <56B8F9CC dot 4080205 at redhat dot com> <56B8FC41 dot 7040107 at redhat dot com>
> On Feb 8, 2016, at 12:36 PM, Carlos O'Donell <firstname.lastname@example.org> wrote:
> Are you familiar with what goes into /etc/ld.so.cache? It is only a cache
> of lookups, not the DSOs themselves, so we would be caching the results of
> a search of the user directories and recording the DSOs found there, nothing
> more. The user is already mostly accustomed to using ldconfig as root to
> update the global cache,
That is probably not true in the cases that Iâm familiar with but I will agree that it could relatively easily be taught. Having them specify the directories that they want searched in a .ld.so.conf or maybe in a .ld.so.conf.appname in the directory for the application could speed things up considerably.
> this is just an extension to allow ldoconfig to
> be run by the user.