Opened 11 years ago

Last modified 7 years ago

#856 closed defect (Implemented)

SIGHUP not compatible with configuring tor over controlport

Reported by: mwenge Owned by:
Priority: Low Milestone:
Component: Core Tor/Tor Version: 0.2.0.31
Severity: Keywords:
Cc: mwenge, nickm, arma Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

The Debian/Ubuntu noreply package of Tor performs regular logrotates on Tor. This results in Tor handling a SIGHUP
and reloading the config from torrc. Any configuration made over the controlport, but not written to torrc, is lost
when this happens.

I suggest that Tor should respect the existing soft configuration during a SIGHUP.

[Automatically added by flyspray2trac: Operating System: All]

Child Tickets

Change History (5)

comment:1 Changed 11 years ago by nickm

Hmm. Perhaps it would be better to have an internal configuration option (prefixed with ) that a controller could
set to override the behavior of SIGHUP and make it not reload torrc?

(It would need some pretty big revisions to the configuration logic to implement something where Tor could tell
controller-set options from torrc-set options.)

comment:2 Changed 11 years ago by nickm

14:09 < nickm> Hi, mwenge! Can you comment on whether the solution I suggested

on bug 856 seems smart to you?

14:11 < mwenge> yes - seems like the way to go.

comment:3 Changed 11 years ago by nickm

Feature implemented in r17567.

comment:4 Changed 11 years ago by nickm

flyspray2trac: bug closed.

comment:5 Changed 7 years ago by nickm

Component: Tor ClientTor
Note: See TracTickets for help on using tickets.