A per-user or per-application ld.so.cache?

[Siddhesh Poyarekar]

On Mon, Feb 08, 2016 at 03:14:08PM -0500, Carlos O'Donell wrote:
> The downside is that the user has no control of this cache and
> would need administrative intervention for help accelerating their
> application. Consider that you bought time on a cluster of machines,
> and now to run your app you're making the user interact with the sysadmin
> to install new filters and run ldconfig on every node? It won't scale
> (from a human perspective).
> 
> With a per-user/per-proces cache say in ~/.ld.so.cache, the user could
> prime the cache themselves after setting up their application with
> bundled libraries and have it work as expected, but accelerated lookups
> without lots of stat/getdents in $HOME.
> 
> Does that counter-argument make sense for why the cache could be
> under user control? It means the data needs to be inspected carefully
> though.

Sure, but a similar effect could also be achieved using
LD_LIBRARY_PATH in ~/.bashrc.

Siddhesh