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.

Is creating a thread expensive?

843

---

Can two threads share the same stack?

846

---

Do threads share variables?

947

---

Why do we need multithreading?

942

---

Explain each system calls used for process management in linux.

923

---

Why thread is faster than process?

866

---

Is multithreading faster than multiprocessing?

961

---

Whats better threading or waxing?

845

---

What is a thread os?

894

---

What are linux kernel threads?

972

---

Why context switching is faster in threads?

873

---

Can we create a thread inside a thread?

945

---

Does hyperthreading reduce performance?

882

---

What does threads mean when downloading?

786

---

What are the two methods to create threads?

902

---