Make it possible to change nameserver options while Tor is running.


svn:r8255

and revise some log severities to match the convention.


svn:r8234

svn:r8222

the config options are bad or good.


svn:r8221

 patch suggested by Karsten Loesing: respond to SIGNAL command before we execute the signal, in case the signal shuts us down.


svn:r7072

svn:r7026

 Add more warnings to the list of those we tolerate. Start using GCC attributes more, for better error checking and better code generation.


svn:r7020

 Shave another 8 bytes from connection_t: turn inbuf_reached_eof into a bit, and lower timestamp_lastempty to or_connection_t


svn:r6934

 Rename some fields, compress a bitfield, and document some structs and fields


svn:r6919

 Clean up wide lines from last patch.


svn:r6907

 Refactor connection_t into edge, or, dir, control, and base subtypes.  This might save some RAM on busy exit servers, but really matters most in terms of correctness.


svn:r6906

config has changed such that we'll want to start advertising our
dirport now, etc.


svn:r6819

svn:r6806

svn:r6805

svn:r6804

requests (so you stop predicting circuits), then hup, then later your
IP changes, you won't think circuits are working so you won't try to
test reachability, so you won't publish.


svn:r6800

svn:r6785

our own descriptor yet.


svn:r6775

MSVC6 is apparently terrified of unnatural cross-breeding between uint64_t and double, and needs more persuasion than usual to cast one to the other.  Issue identified by Frediano Ziglio; patch revised for minimal impact on non-MSVC6 compilers.


svn:r6768

try to rebuild long-term connections to directory authorities, and
directory authorities no longer try to rebuild long-term connections to
all servers.

We still don't hang up connections in these two cases though -- we need
to look at it more carefully to avoid flapping, and we likely need to
wait til 0.1.1.x is obsolete.


svn:r6712

and make the yelling only happen if you're a server.


svn:r6625

is, even tor clients do the same sort of handshake.

this has been true for years, so it's best to get rid of the
stale code.


svn:r6557

Add a new warning to our "warn a lot" list: unused parameters.  This means we have to explicitly "use" unuseds, but it can catch bugs.  (It caught two coding mistakes so far.)


svn:r6532

svn:r6508

svn:r6447

svn:r6421

always IP addresses.


svn:r6389

svn:r6377

svn:r6373

Fix some minor bugs and memory leaks along the way.


svn:r6246

svn:r6226

svn:r6224

expiring connections whenever 5 minutes pass and they *do*
have circuits on them.


svn:r6213

connecting and for resolving). Now we tolerate applications
that don't follow the RFCs. But continue to block malformed
names at the socks side.


svn:r6193

authorities, then don't try to cache any v1 directories.


svn:r6162

svn:r6156

svn:r6143

  1) Surround all constants by (parens), whether we'll be using them
     in a denominator or not.
  2) Express all time periods as products (24*60*60), not as multiplied-out
     constants (86400).
  3) Comments like "(60*60) /* one hour */" are as pointless as comments
     like "c = a + b; /* set c to the sum of a and b */".  Remove them.
  4) All time periods should be #defined constants, not given inline.
  5) All time periods should have doxygen comments.
  6) All time periods, unless specified, are in seconds.  It's not necessary
     to say so.

To summarize, the old (lack of) style would allow:

  #define FOO_RETRY_INTERVAL 60*60 /* one hour (seconds) */
  next_try = now + 3600;

The new style is:

  /** How often do we reattempt foo? */
  #define FOO_RETRY_INTERVAL (60*60)

  next_try = now + RETRY_INTERVAL;


svn:r6142

svn:r6139

svn:r6138