libasyncns is a C library for Linux/Unix for executing name service queries asynchronously. It is an asynchronous wrapper around getaddrinfo(3), getnameinfo(3), res_query(3) and res_search(3) from libc and libresolv. In contrast to GNU's asynchronous name resolving API getaddrinfo_a(), libasyncns does not make use of UNIX signals for reporting completion of name queries. Instead, the API exports a standard UNIX file descriptor which may be integerated cleanly into custom main loops. In contrast to asynchronous DNS resolving libraries like libdenise, skadns, adns, libasyncns is just an asynchronous wrapper around the libc's synchronous getaddrinfo() API, which has the advantage of allowing name resolution using techniques like Multicast DNS, LDAP or NIS using standard libc NSS (Name Service Switch) modules. libasyncns is compatible with IPv6 if the underlying libc is. libasyncns is very tiny, consisting of just one header and one source file. It has no dependencies besides libc. By default libasyncns spawns a number of worker threads (LWPs) to process name queries. Alternatively or when POSIX Threads are not supported, libasyncns can fork() off worker processes instead.
OS | Architecture | Version |
---|---|---|
NetBSD 10.0 | aarch64 | libasyncns-0.8.tgz |
NetBSD 10.0 | aarch64 | libasyncns-0.8.tgz |
NetBSD 10.0 | aarch64 | libasyncns-0.8.tgz |
NetBSD 10.0 | aarch64eb | libasyncns-0.8.tgz |
NetBSD 10.0 | aarch64eb | libasyncns-0.8.tgz |
NetBSD 10.0 | alpha | libasyncns-0.8.tgz |
NetBSD 10.0 | alpha | libasyncns-0.8.tgz |
NetBSD 10.0 | earmv4 | libasyncns-0.8.tgz |
NetBSD 10.0 | earmv6hf | libasyncns-0.8.tgz |
NetBSD 10.0 | earmv6hf | libasyncns-0.8.tgz |
NetBSD 10.0 | earmv6hf | libasyncns-0.8.tgz |
NetBSD 10.0 | earmv7hf | libasyncns-0.8.tgz |
NetBSD 10.0 | earmv7hf | libasyncns-0.8.tgz |
NetBSD 10.0 | earmv7hf | libasyncns-0.8.tgz |
NetBSD 10.0 | i386 | libasyncns-0.8.tgz |
NetBSD 10.0 | i386 | libasyncns-0.8.tgz |
NetBSD 10.0 | i386 | libasyncns-0.8.tgz |
NetBSD 10.0 | m68k | libasyncns-0.8.tgz |
NetBSD 10.0 | powerpc | libasyncns-0.8.tgz |
NetBSD 10.0 | powerpc | libasyncns-0.8.tgz |
NetBSD 10.0 | sparc64 | libasyncns-0.8.tgz |
NetBSD 10.0 | sparc64 | libasyncns-0.8.tgz |
NetBSD 10.0 | sparc | libasyncns-0.8.tgz |
NetBSD 10.0 | sparc | libasyncns-0.8.tgz |
NetBSD 10.0 | vax | libasyncns-0.8.tgz |
NetBSD 10.0 | vax | libasyncns-0.8.tgz |
NetBSD 10.0 | x86_64 | libasyncns-0.8.tgz |
NetBSD 10.0 | x86_64 | libasyncns-0.8.tgz |
NetBSD 10.0 | x86_64 | libasyncns-0.8.tgz |
NetBSD 9.0 | aarch64 | libasyncns-0.8.tgz |
NetBSD 9.0 | aarch64 | libasyncns-0.8.tgz |
NetBSD 9.0 | aarch64 | libasyncns-0.8.tgz |
NetBSD 9.0 | alpha | libasyncns-0.8.tgz |
NetBSD 9.0 | alpha | libasyncns-0.8.tgz |
NetBSD 9.0 | earmv4 | libasyncns-0.8.tgz |
NetBSD 9.0 | earmv6hf | libasyncns-0.8.tgz |
NetBSD 9.0 | earmv6hf | libasyncns-0.8.tgz |
NetBSD 9.0 | earmv6hf | libasyncns-0.8.tgz |
NetBSD 9.0 | earmv7hf | libasyncns-0.8.tgz |
NetBSD 9.0 | earmv7hf | libasyncns-0.8.tgz |
NetBSD 9.0 | earmv7hf | libasyncns-0.8.tgz |
NetBSD 9.0 | i386 | libasyncns-0.8.tgz |
NetBSD 9.0 | i386 | libasyncns-0.8.tgz |
NetBSD 9.0 | i386 | libasyncns-0.8.tgz |
NetBSD 9.0 | powerpc | libasyncns-0.8.tgz |
NetBSD 9.0 | powerpc | libasyncns-0.8.tgz |
NetBSD 9.0 | powerpc | libasyncns-0.8.tgz |
NetBSD 9.0 | sparc64 | libasyncns-0.8.tgz |
NetBSD 9.0 | x86_64 | libasyncns-0.8.tgz |
NetBSD 9.0 | x86_64 | libasyncns-0.8.tgz |
NetBSD 9.0 | x86_64 | libasyncns-0.8.tgz |
NetBSD 9.3 | x86_64 | libasyncns-0.8.tgz |
NetBSD 9.3 | x86_64 | libasyncns-0.8.tgz |
Binary packages can be installed with the high-level tool pkgin (which can be installed with pkg_add) or pkg_add(1) (installed by default). The NetBSD packages collection is also designed to permit easy installation from source.
The pkg_admin audit command locates any installed package which has been mentioned in security advisories as having vulnerabilities.
Please note the vulnerabilities database might not be fully accurate, and not every bug is exploitable with every configuration.
Problem reports, updates or suggestions for this package should be reported with send-pr.