Don't allocate additional memory in the trie if we are over the limit.

After reconnecting, either ignore the config update (if the config is
the same we have) or wipe out the old config first to free the memory.

Use sanity instead of assert. The advantage is it logs in a way that is
sent to the server. It may help find the crash-bug there somewhere.

Do the commit at the end. There's nothing gained by commiting during the
read.

As the flag is very slow during the updates.

If the database is very slow or blocked somehow, run only one instance.
There's no point in running several in a row when it unblocks. Also,
such thing stresses the DB unnecessarily.

If it is already running, don't start another instance. Or, more
exactly, terminate it right away.

Each item of the biflows table is updated once during its life, so leave
space for the updated entry there.

Fix bug causing the fake log to send after each event.

There seems to be some stack corruption. It shouldn't possibly in the
signal handler, but rewrite it all the same.

Call gdb on self to obtain backtrace and other info and put it to logs.

It timeouts a lot. See if increasing would help.

Include IP addresses of some TLD DNS servers often used for malware. Tag
them in the database.

Disconnect from DB for the time WHOIS queries are running. And try to
die in case of timeout, since the whois_query seems not to be doing
that.

Make sure the routers that have only firewall activity aren't skipped
over due to complexities in the query.

Don't think you're online unless you get a confirmation from the server.

Use sanity() instead of several cases of assert(), die() or abort().

Similar to assert, but with a message and not possible to exclude from
compilation. This is better for checking outputs, for example.

Since it signals broken message by returning NULL, not by calling die
directly.

The index is received from the server. We would be in far deeper trouble
if someone could impersonate our server than to crash the client, but it
should be fixed anyway.

Don't crash, but handle it gracefully. This is, however, only
testing/example code, so there was no impact on production in this bug.