Timeline for Why is the configuration generated with Arm's setup not persistent?
Current License: CC BY-SA 3.0
9 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Sep 20, 2015 at 13:31 | comment | added | doobadooba |
Indeed. Nevertheless, the core problem is that the Arm Wizard edits a torrc file which is not persistent across reboots (regardless of whether one “forgets to restart tor“). Only the manual editing of /etc/tor/torrc solved it for me.
|
|
Sep 20, 2015 at 13:25 | vote | accept | doobadooba | ||
Sep 20, 2015 at 13:09 | comment | added | Ron | @doobadooba yes, as "...people who edit their torrc, forget to restart tor, and are then confused why the settings didn't take effect." ;) Edited by question. You may accept it as the answer if it helped you ;) | |
Sep 20, 2015 at 13:07 | history | edited | Ron | CC BY-SA 3.0 |
added 216 characters in body
|
Sep 20, 2015 at 13:01 | comment | added | doobadooba |
Ah! I had to start Tor again via the /arm/startTor script -- it was my understanding that Tor would start by itself at reboot (as a "deamon"), but it does not. So, replacing the contents of /etc/tor/torrc with those of ~/.arm/torrc solves my problem. @Ron, can you edit your answer, or write a new one with this?
|
|
Sep 20, 2015 at 12:52 | comment | added | doobadooba |
I replaced /etc/tor/torrc with ~/.arm/torrc (the file that resulted from Arm Setup Wizard), and now when I launch arm , I am immediately prompted by the Wizard again… my settings have somehow been lost. What am I doing wrong?
|
|
Sep 20, 2015 at 9:05 | comment | added | Ron |
Simplest solution is to edit the /etc/tor/torrc file, restart tor and then launch arm and ignore the message.
|
|
Sep 20, 2015 at 7:58 | comment | added | doobadooba | The message itself is not my problem… what I am concerned about is that every time I reboot, I have to re-configure Tor through Arm so that my relay runs with my configuration. | |
Sep 20, 2015 at 7:22 | history | answered | Ron | CC BY-SA 3.0 |