These scripts are now a little more bulletproof, cache data a little
better, and generate more information.  Notably, they search for the
vectors or edges to cut that would lower the size of the largest
SCC.

(Change not made in torrc.minimal.in; only in torrc.sample and
torrc.minimal.in-staging)

Closes ticket 16742.

Signed-off-by: David Goulet <dgoulet@ev0ke.net>

Fixes bug 16539; bugfix on 0.2.7.2-alpha.

See ticket 16762.

This should simplify the callgraph a little more.

David Goulet authored Aug 05, 2015 and Nick Mathewson committed Aug 11, 2015

Signed-off-by: David Goulet <dgoulet@ev0ke.net>

David Goulet authored Aug 05, 2015 and Nick Mathewson committed Aug 11, 2015

Signed-off-by: David Goulet <dgoulet@ev0ke.net>

David Goulet authored Jun 25, 2015 and Nick Mathewson committed Aug 11, 2015

Signed-off-by: David Goulet <dgoulet@ev0ke.net>

David Goulet authored Jun 25, 2015 and Nick Mathewson committed Aug 11, 2015

Safer, wiser, stronger!
Signed-off-by: David Goulet <dgoulet@ev0ke.net>

David Goulet authored Jun 25, 2015 and Nick Mathewson committed Aug 11, 2015

Signed-off-by: David Goulet <dgoulet@ev0ke.net>

David Goulet authored Jun 18, 2015 and Nick Mathewson committed Aug 11, 2015

When fetching a descriptor, we know test every introduction points in it
against our rend failure cache to know if we keep it or not. For this to
work, now everytime an introduction points is discareded (ex: receiving a
NACK), we note it down in our introduction cache.

See rendcache.c for a detailed explanation of the cache's behavior.

Fixes #16389
Signed-off-by: David Goulet <dgoulet@ev0ke.net>

When we removed Running/Valid checks from Fast and Stable in 8712, I
removed them from HSDir too, which apparently wasn't a good idea.

Reverts part of a65e8358.  Fixes bug 16524. Bugfix
on 0.2.7.2-alpha.

microdesc_free_() called get_microdesc_cache(), which had the fun
side-effect of potentially reloading the whole cache from disk.
Replace it with a variant that doesn't.

Closes ticket 16734.

If setrlimit() failed, max_out wasn't set in set_max_file_descriptors()
ending in a state where we don't use ULIMIT_BUFFER for things like tor
private key files.

Also fix the set_max_file_descriptors() documentation.

Fixes #16274
Signed-off-by: David Goulet <dgoulet@ev0ke.net>

cypherpunks authored Jul 23, 2015 and Nick Mathewson committed Aug 04, 2015

According to POSIX, the mutex must be locked by the thread calling the signal
functions to ensure predictable scheduling behavior.

Found the issue using Helgrind which gave the warning `dubious: associated lock
is not held by any thread`.