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.

Can threading damage skin?

823

---

Are threads processes?

845

---

Can a thread have multiple processes?

829

---

What is a thread os?

857

---

What do cores and threads do?

913

---

What is the difference between process and thread in linux?

826

---

What is difference between thread and runnable?

881

---

Can two threads share the same stack?

807

---

How do I see threads in linux?

908

---

Whats better threading or waxing?

812

---

Which way of creating thread is better?

752

---

What is posix thread linux?

775

---

What is the main disadvantage of user level threads?

843

---

What does threads mean when downloading?

753

---

How many threads can a cpu run?

854

---