Answer Posted / manoj

This is one system administrator's point of view why
LD_LIBRARY_PATH, as frequently used, is bad. This is written
from a SunOS 4.x/5.x (and to some extent Linux) point of
view, but this also applies to most other UNIXes.

LD_LIBRARY_PATH is an environment variable you set to give
the run-time shared library loader (ld.so) an extra set of
directories to look for when searching for shared libraries.
Multiple directories can be listed, separated with a colon
(:). This list is prepended to the existing list of
compiled-in loader paths for a given executable, and any
system default loader paths.

For security reasons, LD_LIBRARY_PATH is ignored at runtime
for executables that have their setuid or setgid bit set.
This severely limits the usefulness of LD_LIBRARY_PATH.

What are the differences between user level threads and kernel threads?

756

---

What are threads and processes?

841

---

Whats the difference between a thread and a process?

779

---

Is creating a thread expensive?

747

---

Why is threading bad for you?

753

---

Do threads count as cores?

797

---

Why are threads useful?

802

---

What are processes and threads?

831

---

Can two threads execute at the same time?

755

---

Can one thread run on multiple cores?

728

---

Do threads get their own pid?

769

---

Is c++ multithreaded?

727

---

What does threads mean when downloading?

703

---

What is pthread in linux?

768

---

Can threading damage skin?

765

---