On Thu, 04 Aug 2016, tor relay wrote:
On August 3, 2016 at 11:51 PM Green Dream greendream848@gmail.com wrote:
Sorry, I didn't understand that your daemon didn't restart after the upgrade. I ran through the upgrade on 2 relays, and apt started the service post-upgrade on both.
Since it is reproducible in my case as well I assume you do _not_ have the following constellation:
tor.service is disabled and stopped (I don't use the default instance)
You should not disable tor.service.
tor.service is what controls all tor instances. The default service is tor@default.service. If you don't want it to start, one option is to move away /etc/tor/torrc.