On Thu, Jan 19, 2017 at 01:55:10PM +1100, teor wrote:
> Occasionally, the tor process fails to shut down a pluggable transport
> process when tor exits. I believe this is an unavoidable consequence of
> unexpected or unclean tor shutdowns or crashes.
Right. This is why we changed the design in
> On 19 Jan 2017, at 13:46, Geoff Down wrote:
>
> On Thu, Jan 19, 2017, at 02:33 AM, teor wrote:
>>
>>> On 19 Jan 2017, at 13:30, Geoff Down wrote:
>
>>> Then a HUP produced the same sequence (but a different PID), with no
>>> sign of the lines
On Thu, Jan 19, 2017, at 02:33 AM, teor wrote:
>
> > On 19 Jan 2017, at 13:30, Geoff Down wrote:
> > Then a HUP produced the same sequence (but a different PID), with no
> > sign of the lines you mention above regarding 'restart'.
> > The original obsfproxy process 17356
> On 19 Jan 2017, at 13:30, Geoff Down wrote:
>
>
> On Thu, Jan 19, 2017, at 01:14 AM, teor wrote:
>>
>>> On 19 Jan 2017, at 12:00, Geoff Down wrote:
>>> Jan 19 00:47:42.000 [notice] Tor 0.2.9.8 opening log file.
>>> Jan 19 00:47:55.000 [warn]
On Thu, Jan 19, 2017, at 01:14 AM, teor wrote:
>
> > On 19 Jan 2017, at 12:00, Geoff Down wrote:
> > Jan 19 00:47:42.000 [notice] Tor 0.2.9.8 opening log file.
> > Jan 19 00:47:55.000 [warn] Server managed proxy encountered a method
> > error. (obfs3 Could not set up
> On 19 Jan 2017, at 12:00, Geoff Down wrote:
>
> Hi,
> I sent a SIGHUP to the tor process after altering the torrc and got this
> effect:
> Jan 19 00:47:42.000 [notice] Tor 0.2.9.8 opening log file.
> Jan 19 00:47:55.000 [warn] Server managed proxy encountered a method
Hi,
I sent a SIGHUP to the tor process after altering the torrc and got this
effect:
Jan 19 00:47:42.000 [notice] Tor 0.2.9.8 opening log file.
Jan 19 00:47:55.000 [warn] Server managed proxy encountered a method
error. (obfs3 Could not set up listener (0.0.0.0:x) for 'obfs3'
(Address already