tor/changes/bug10449

  o Minor bugfixes:
    - Exit immediately when exiting because of dropped connection from
      a process-owning controller. Previously, if we were running in
      server mode, we would wait for a little while as in the when we
      got an INT signal--but this was problematic, since there was no
      feedback for the user. Controllers that want to do a clean
      shutdown should send an INT signal, and let the user know what's
      going on. Fix for bug 10449; bugfix on 0.2.2.28-beta.
bug10449: a dying owning controller makes Tor exit immediately If you want a slow shutdown, send SIGNAL SHUTDOWN. (Why not just have the default be SIGNAL QUIT? Because this case should only happen when an owning controller has crashed, and a crashed controller won't be able to give the user any "tor is shutting down" feedback, and so the user gets confused for a while. See bug 10449 for more info) 2014-02-03 18:54:06 +01:00			`o Minor bugfixes:`
			`- Exit immediately when exiting because of dropped connection from`
			`a process-owning controller. Previously, if we were running in`
			`server mode, we would wait for a little while as in the when we`
			`got an INT signal--but this was problematic, since there was no`
			`feedback for the user. Controllers that want to do a clean`
			`shutdown should send an INT signal, and let the user know what's`
			`going on. Fix for bug 10449; bugfix on 0.2.2.28-beta.`