Public bug reported:
Very often I run "ldconfig" and I wait a long long time only to tell me that it
can't write to /etc/something
This is my own fault because I forgot to write "sudo" in front of the
"ldconfig" and that's fine.
However, ldconfig should not do all the work first and then check if the file
is writable.
It would provide a much better user experience if ldconfig would immediately on
startup verify that it has permissions to write to /etc/*SOME_NEED_FILES*, then
do the work that takes a long time, and then finally write the updated SO cache
info to the file in /etc/SOME_FILE
Just because it's a _command line_ tool for _developers_ does not mean
it can't have "usability" or be smart about these things. And it's also
an easy thing to fix I suspect.
** Affects: glibc (Ubuntu)
Importance: Undecided
Status: New
--
ldconfig should check immediately on startup whether it can write to /etc/* or
not
https://bugs.launchpad.net/bugs/271831
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
