> On 07/09/2015 03:24 PM, aexlfowley at web.de wrote:
>> Correct. I edited /lib/systemd/system/tor.service and added
>> ReadWriteDirectories=-/media/cRAID/Tor
>> and now 0.2.6.9 is running.
>> I'm not entirely sure how to create my own
>> /etc/systemd/sy
> On Tue, 07 Jul 2015, aexlfowley at web.de wrote:
>
>> After upgrading from 0.2.5.12 (git-3731dd5c3071dcba) to 0.2.6.9
>> (git-145b2587d1269af4) an error occured.
>> I'm on Debian Jessie (stable) on an AMD Athlon 64 X2. Tor won't start
>> and these are t
>> On 8 Jul 2015, at 08:06 , l.m wrote:
>>
>> Sounds like access control gone wrong. An older version works but a newer
>> version fails. Permissions on the filesystem look fine from mount output. So
>> do you use access control, apparmor, selinux, grsecurity, fsprotect,
>> bilibop, etc? In pa
> Sounds like access control gone wrong. An older version works but a
> newer version fails. Permissions on the filesystem look fine from
> mount output. So do you use access control, apparmor, selinux,
> grsecurity, fsprotect, bilibop, etc? In particular the tor package
> which is mentioned in you
Hi devs,
User here. teor send me over from IRC. It's regarding to this
trac-ticket https://trac.torproject.org/projects/tor/ticket/16518
After upgrading from 0.2.5.12 (git-3731dd5c3071dcba) to 0.2.6.9
(git-145b2587d1269af4) an error occured.
I'm on Debian Jessie (stable) on an AMD Athlon 64 X2. To
