SIGHUP not compatible with configuring tor over controlport
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]