When should we use thread-safe "_r" library calls?
Answers were Sorted based on User's Feedback
Answer / guest
If your system provides threads, it will probably provide a
set of thread-safe variants of standard C library routines.
A small number of these are mandated by the POSIX standard,
and many Unix vendors provide their own useful supersets,
including functions such as gethostbyname_r().
Unfortunately, the supersets that different vendors support
do not necessarily overlap, so you can only safely use the
standard POSIX-mandated functions. The thread-safe routines
are conceptually "cleaner" than their stateful
counterparts, though, so it is good practice to use them
wherever and whenever you can.
Is This Answer Correct ? | 4 Yes | 0 No |
Answer / vidya
If you compile using _REENTRANT option, the thread-safe
functions are automatically substituted for the non thread
safe function. You need not specify *_r, you only use *
Is This Answer Correct ? | 0 Yes | 0 No |
How to work unix commands on windows xp without installing unix o/s in pc?
what is Scheduling?
What are the main families of threads?
Tell me when should we use thread-safe "_r" library calls?
Explain what is critical section?
What is protection boundary?
When should we use thread-safe "_r" library calls?
explain about the initial process sequence while the system boots up?
what is Context switch?
Explain the different kinds of threads?
Explain the architectural differences between user-space threads, and kernel-supported threads?
If your server is running on Unix and one of the sessions are keep on running without loading any data. how would you kill it?