tor/changes/bug5095

  o Minor bugfixes:
    - When we receive a SIGHUP and the controller-use __ReloadTorrcOnSIGHUP
      option is set to 0, perform other actions that SIGHUP usually causes
      (like reopening the logs). Fixes bug 5095; bugfix on 0.2.1.9-alpha.
When ReloadTorrcOnSIGHUP=1, do non-reload activities anyway Previously, we skipped everything that got invoked from options_init_from_torrc. But some of the stuff in options_act_reversible and options_act is actually important, like reopening the logs. Now, a SIGHUP always makes the effects of an options_set() happen, even though the options haven't changed. Fix for bug 5095; bugfix on 0.2.1.9-alpha, which introduced __ReloadTorrcOnSIGHUP. 2012-04-11 20:47:42 +02:00			`o Minor bugfixes:`
			`- When we receive a SIGHUP and the controller-use __ReloadTorrcOnSIGHUP`
			`option is set to 0, perform other actions that SIGHUP usually causes`
			`(like reopening the logs). Fixes bug 5095; bugfix on 0.2.1.9-alpha.`