Searched refs:thread (Results 1 – 3 of 3) sorted by relevance
| /resolv/ |
| A D | Makefile | 80 ifeq ($(have-thread-library),yes)
118 tst-resolv-res_init-thread \
212 $(objpfx)libanl.so: $(shared-thread-library)
214 $(objpfx)tst-res_hconf_reorder: $(shared-thread-library)
240 $(objpfx)tst-bug18665: $(objpfx)libresolv.so $(shared-thread-library)
243 $(objpfx)libresolv.so $(shared-thread-library)
245 $(objpfx)libresolv.so $(shared-thread-library)
256 $(shared-thread-library)
257 $(objpfx)tst-resolv-res_init-thread: $(objpfx)libresolv.so \
258 $(shared-thread-library)
[all …]
|
| A D | README | 9 the parts needed to provide thread-safety. This means that support
33 state first. Note that the thread-safe `res_nclose' still doesn't
48 interfaces are not thread-safe. Therefore, BIND 8.2 introduced a set
51 argument, so you can use a per-thread resolver state. In glibc, when
52 you link with -lpthread, such a per-thread resolver state is already
57 `gethostbyname_r' is now fully thread-safe and re-entrant. The
59 resolver state and are therefore still thread-unsafe. The resolver
61 thread.
70 in the "main" thread should continue to work, except that they no
79 than the "main" thread will seem to have no effect though.
[all …]
|
| A D | tst-resolv-threads.c | 64 int thread = 0; in response() local
67 &counter, &thread, &dummy) == 2); in response()
80 char ipv4[4] = {10, 0, counter, thread}; in response()
88 counter, 0, thread, 0, 0}; in response()
|
Completed in 9 milliseconds