- the test driver now waits for daemon to accept TCP
- workaround cwrap bug, Python prebinds to daemon sockets to create files
- tested daemon runs in the testdir
- test driver doesn’t kill all kresd processes

- no need to bind to client socket
- relying on short timeouts is bad
- no check for send buffers overflow

this is a workaround, as we don't support `make uninstall` yet

zonecut should be able to hold these for testing reasons (like private
root or zone cut), but it should filter out data from the internet
a new flag: QUERY_ALLOW_LOCAL allows for being more permissive, and
letting name server query local or private address ranges

this is not documented atm as it is going to change for a module with
declarative interface and less cryptic names

this is a small step for me, but a huge step for resolver

based on _BSD_SOURCE timersub macro

this fixes stats for canceled/blocked or forwarded queries without
started name resolution

this also fixes static linking missing a math library

this is a first step of leaning towards LuaJIT.
the FFI bindings are much faster, simpler and don’t abort traces

daemon core scripting engine is still going to support interpreted Lua, but modules requiring library bindings (such as ‘block’) will require LuaJIT for FFI

previously the pointer for C layer API was stored in Lua, it is stored directly in module data now for fast access. this doesn’t disturb VM when processing requests.

this provides a useful callback for per-request operations that can’t wait until the query is completed (e.g. blocking or logging started queries)

the memory could go through the roof with sufficiently high pps, GC now runs at 4x the speed of allocations and doesn’t wait for increase, some callbacks also perform full collection cycle on completion