[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#72140: Setting up libraries too slow

On Fri, 22 Sep 2000, Wichert Akkerman wrote:

> > So what? If one cannot write the cache, the next process will run into the
> > same problem. The user won't notice that unless he/she/it runs
> > strace. On occasion, root may run a program and then the cache gets
> > updated.

> In other words it is a useless thing anyway and you might as well ask
> root to run ldconfig.

Nope, this involves manual action by root. The cache can also get updated
when a cron job starts some program with root perms.

> I don't like things being needlessly smart to hide the fact that
> something should be done.

Well, this is the way a cache is supposed to work: It speeds up things,
but it doesn't get in the way of normal operation. I wouldn't consider
that "needlessly smart" but a minimal requirement. Imagine I had to tell
my http proxy that it should check whether the documents it serves are
still up to date.

> > Yes they do, if they install software into /usr/local. This is a common
> > setup in university labs.

> Only admins can do that, and they know how to run ldconfig.

drwxrwsr-t  47 root   dist     1536 Jul 26 22:39 /usr/local/dist/DIR/

> The dynamic linker has no bussiness do anything except dynamically
> linking things.

It is supposed to update its cache if it is outdated IMO.


PGP public key available from http://phobos.fs.tum.de/pgp/Simon.Richter.asc
 Fingerprint: 10 62 F6 F5 C0 5D 9E D8  47 05 1B 8A 22 E5 4E C1
Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!

Reply to: