Your message dated Mon, 6 Jun 2011 08:31:05 +0200
with message-id <[email protected]>
and subject line Re: __ReloadTorrcOnSIGHUP option
has caused the Debian Bug report #558603,
regarding tor: frequently closes orport without user interaction
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
558603: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=558603
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: tor
Version: 0.2.1.20-2
Severity: important
My system has limits on the allowed traffic that change during the day.
I therefore configure tor in a way producing little traffic and open the
ORPort during the "happy hours". Unfortunately tor manages to close the
ORPort before the happy hours end. As it happens during the morning I
assume tor rereads the configuration. This seems to completely defeat
the purpose of the ControlPort.
Helmut
--- End Message ---
--- Begin Message ---
On Thu, Apr 21, 2011 at 12:14:42PM +0200, [email protected] wrote:
> since 0.2.1.9-alpha, Tor has had "an internal-use-only
> __ReloadTorrcOnSIGHUP option for controllers to prevent SIGHUP from
> reloading the configuration".
>
> See the bug report that triggered the addition of this option for
> details: https://trac.torproject.org/projects/tor/ticket/856
>
> Helmut, would you object if the Debian bug you submitted (#558603) was
> closed?
No, I would not, cause it solves the initial issue.
Helmut
--- End Message ---
