>> Maybe it is best to ask what you are trying to achieve.
>
> Nothing special? I don't gather what is extended or here in the config?
"ExtORPort auto"
this relay:
https://metrics.torproject.org/rs.html#details/8E3D3C5B64A8DAD9152687C93CDCE1D98CC5E325
seems to be doing fine.
Some configuration l
On 12-03-18 17:41, nusenu wrote:
> your logs hint towards non-"basic" configuration items (i.e. extended OR).
SocksPort 127.0.0.1:9050
Log notice file /var/log/tor/notices.log
RunAsDaemon 1
DataDirectory /var/lib/tor
ControlPort 9051
HashedControlPassword
16:95A7D8C558E41A556QF4D65351CEAA8D959DQA7
Udo van den Heuvel:
> On 12-03-18 09:34, nusenu wrote:
I recommend you use the service file shipped by fedora's tor package.
>>>
>>> That service file needs the same capabilities addition...
>>
>> If you want, I can look into this but I will need some more information:
>> * how do you instal
On 12-03-18 09:34, nusenu wrote:
>>> I recommend you use the service file shipped by fedora's tor package.
>>
>> That service file needs the same capabilities addition...
>
> If you want, I can look into this but I will need some more information:
> * how do you install tor from what source (dnf i
George:
> Udo van den Heuvel:
>> Hello,
>>
>> After migration to a fresh new box, tor runs but does not create
>> /var/log/tor/notices.log anymore.
>> Config was unchanged.
>> Permissions on /var/log/tor appear OK.
>>
>> How can I fix this?
>
> Log files aren't necessarily created. You may need
Udo van den Heuvel:
> On 11-03-18 10:54, nusenu wrote:
>>> When trying to start tor using the default service file
>>> contrib/dist/tor.service on a Fedora 26 system with kernel.org kernel we
>>> see a failure to start:
>>
>> I recommend you use the service file shipped by fedora's tor package.
>
