Does this apply only to Debian, or Linux in general?
On Saturday, July 2, 2016, Green Dream wrote:
>
> don't run arm as the tor user, Roger tells you why:
>> https://lists.torproject.org/pipermail/tor-relays/2016-May/009259.html
>
>
>
> Interesting. I didn't know this, and I've always used "sudo
> don't run arm as the tor user, Roger tells you why:
> https://lists.torproject.org/pipermail/tor-relays/2016-May/009259.html
Interesting. I didn't know this, and I've always used "sudo -u" as well.
Thanks for sharing.
For the archives, the link above ultimately leads here:
https://www.torproj
>>> SocksPort auto
>>> RunAsDaemon 0
>>> Log notice file /var/log/tor/notices2.log
>>> ControlPort 9052
>>> HashedControlPassword xx:xx
>>> Nickname test2
>>> RelayBandwidthRate 500 KB
>>> RelayBandwidthBurst 800 KB
>>
>> This is lacking the configuration of a separate DataDirectory and
>>
On Sat, 02 Jul 2016, pa011 wrote:
> Ok - "Log notice file /var/log/tor/notices2.log" removed from torrc, but
> that doesn’t influence the error message from systemctl in no way.
>
> Still not working !
Please try to provide at least some more useful information.
(Also, please stop top posting an
On Sat, 02 Jul 2016, Moritz Bartl wrote:
> On 07/02/2016 04:02 PM, pa011 wrote:
> > SocksPort auto
> > RunAsDaemon 0
> > Log notice file /var/log/tor/notices2.log
> > ControlPort 9052
> > HashedControlPassword xx:xx
> > Nickname test2
> > RelayBandwidthRate 500 KB
> > RelayBandwidthBurst 8
On 07/02/2016 04:02 PM, pa011 wrote:
> SocksPort auto
> RunAsDaemon 0
> Log notice file /var/log/tor/notices2.log
> ControlPort 9052
> HashedControlPassword xx:xx
> Nickname test2
> RelayBandwidthRate 500 KB
> RelayBandwidthBurst 800 KB
This is lacking the configuration of a separate DataD
Ok - "Log notice file /var/log/tor/notices2.log" removed from torrc, but
that doesn’t influence the error message from systemctl in no way.
Still not working !
Does the machine on which I like to add this second instance have more
than one core??
I don’t want to use ansible at the moment - that
> Still unsuccessful, even after reboot -here is what I did:
>
> sudo tor-instance-create tor2
>
> sudo adduser xxx _tor-tor2
no need to create that user manually, tor-instance-create does that
> sudo systemctl start tor@tor2
>
> Job for tor@tor2.service failed. See 'systemctl status tor@tor2
Still unsuccessful, even after reboot -here is what I did:
sudo tor-instance-create tor2
sudo adduser xxx _tor-tor2
sudo systemctl start tor@tor2
Job for tor@tor2.service failed. See 'systemctl status tor@tor2.service'
and 'journalctl -xn' for details.
xxx@xxx:~$ systemctl status tor@tor2.serv
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I do run a Tor exit relay under a 64 bit hardened Gentoo as OS and do wonder
about a Trac issue reported in [1]. About 2/3 of all closed onion connections
returns IOERROR instead of DONE as seen using [2]. That's why I'm asking here
if other made
> Ok - I do have it and I installed a second instance called "tor2".
>
> I can control the first instance of Tor as usual with arm but how can I
> now control the running of "tor2" with arm?
>
> When calling arm with "sudo -u _tor-tor2 arm"
don't run arm as the tor user, Roger tells you why:
http
Ok - I do have it and I installed a second instance called "tor2".
I can control the first instance of Tor as usual with arm but how can I
now control the running of "tor2" with arm?
When calling arm with "sudo -u _tor-tor2 arm" I get asked for a
Controller password even while having a HashedCont
12 matches
Mail list logo
