4 Aug
2016
4 Aug
'16
5:44 a.m.
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) tor@1 mailto:tor@1 .service is enabled and running tor@2.service mailto:tor@2.service is enabled and running