diff options
| author | Nick Mathewson <nickm@torproject.org> | 2014-02-03 12:54:06 -0500 |
|---|---|---|
| committer | Nick Mathewson <nickm@torproject.org> | 2014-02-03 12:54:06 -0500 |
| commit | f96400d9df4cdf22db0c473be21024b60673b786 (patch) | |
| tree | 15af08b651eac6dc0b0f753fdf7b242ee620f752 /changes | |
| parent | 696b484d4dc2e78ff8cf0f7c512d0dc3297197d9 (diff) | |
| download | tor-f96400d9df4cdf22db0c473be21024b60673b786.tar tor-f96400d9df4cdf22db0c473be21024b60673b786.tar.gz | |
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)
Diffstat (limited to 'changes')
| -rw-r--r-- | changes/bug10449 | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/changes/bug10449 b/changes/bug10449 new file mode 100644 index 000000000..93811f07b --- /dev/null +++ b/changes/bug10449 @@ -0,0 +1,8 @@ + 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.
\ No newline at end of file |