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 is difference between thread and runnable?

876

---

Can two threads share the same stack?

796

---

Can threading damage skin?

814

---

What is the difference between user level thread and kernel level thread?

756

---

What is the biggest advantage of implementing threads in user space?

884

---

Can a process have 0 threads?

800

---

Does thread count matter cpu?

773

---

What is the main disadvantage of user level threads?

840

---

Do threads count as cores?

875

---

Can one thread run on multiple cores?

770

---

Do threads share heap?

859

---

What is user level and kernel level thread?

807

---

Why are threads useful?

853

---

What is hyperthreading good for?

792

---

How many cores and threads do I need?

881

---