tor/changes/bug1992

  o Minor bugfixes:
    - Stop trying to resolve our hostname so often (e.g. every time we
      think about doing a directory fetch). Now we reuse the cached
      answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
      and 2410 (bugfix on 0.1.2.2-alpha).

  o Minor features:
    - Make bridge relays check once a minute for whether their IP
      address has changed, rather than only every 15 minutes. Resolves
      bugs 1913 and 1992.
Stop trying to resolve our hostname so often For example, we were doing a resolve every time we think about doing a directory fetch. Now we reuse the cached answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc) and 2410 (bugfix on 0.1.2.2-alpha). 2013-02-12 03:48:18 +01:00			`o Minor bugfixes:`
			`- Stop trying to resolve our hostname so often (e.g. every time we`
			`think about doing a directory fetch). Now we reuse the cached`
			`answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)`
			`and 2410 (bugfix on 0.1.2.2-alpha).`

Check for IP address change every minute, not 15 minutes Relays used to check every 10 to 60 seconds, as an accidental side effect of calling directory_fetches_from_authorities() when considering doing a directory fetch. The fix for bug 1992 removes that side effect. At the same time, bridge relays never had the side effect, leading to confused bridge operators who tried crazy tricks to get their bridges to notice IP address changes (see ticket 1913). The new behavior is to reinstate an every-60-seconds check for both public relays and bridge relays, now that the side effect is gone. 2013-02-12 03:57:32 +01:00			`o Minor features:`
			`- Make bridge relays check once a minute for whether their IP`
			`address has changed, rather than only every 15 minutes. Resolves`
			`bugs 1913 and 1992.`