Date: Sat, 08 Jul 2000 22:14:20 +0200 From: Maxime Henrion <mhenrion@cybercable.fr> To: freebsd-hackers@freebsd.org Subject: ldconfig behaviour when no parameters are given Message-ID: <39678B9C.C9166C11@cybercable.fr>
next in thread | raw e-mail | index | archive | help
Hi everybody,
When ldconfig is invoked without any parameters, the shared library
cache is reseted to the contents of /usr/lib only. I think such a
behaviour isn't very useful, especially when one knows that a lot of
people come to FreeBSD after having used Linux. The first time they get
an error message like "foo.so not found", they, nearly automatically,
run ldconfig and so screw up their shared library cache.
Is there a special reason why ldconfig behaves this way ? And is
there any application that rely on that behaviour ? This would at least
estonish me. That's why, i wanted to suggest that ldconfig prints a
usage screen when invoked without parameters, or else that it performs a
default and safe action, like a refresh (ldconfig -R).
If it happens that what I say make sense, and that the two
requirements above are met (see the two questions), i'll be happy to
submit a patch.
Waiting for your comments,
- Maxiime Henrion
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?39678B9C.C9166C11>