This is the mail archive of the mailing list for the glibc project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: A per-user or per-application

On Mon, Feb 08, 2016 at 01:40:05PM -0500, Carlos O'Donell wrote:
> Under what conditions might it make sense to implement
> a per-user
> At Red Hat we have some customers, particularly in HPC,
> which deploy quite large applications across systems that
> they don't themselves maintain. In this case the given
> application could have thousands of DSOs. When you load
> up such an application the normal search paths apply
> and that's not very optimal.
> Might it make sense to have a per-user for
> this case? Might we even entertain a per-application

It won't be a bad idea as long as it is ignored when running setuid

The other alternative could be extending to have profiles
for specific binaries in the system path.  That is, enhance the format
of files in /etc/ to have a regular expression (or maybe
even simple wildcards) in the beginning that specifies binaries that
will use these paths first.  IIRC we do something similar for hwcaps.

This should also improve performance marginally for applications that
don't need all of those library paths that the files in
add.  It will also help maintain a clean namespace in cases where two
installations may have DSOs with the same names but in different


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]