[tor-dev] tor#16518: Read-Only Filesystem Error opening tor lockfile in 0.2.6.9 but not 0.2.5.12

[aexlfowley at web.de]

>> On 8 Jul 2015, at 08:06 , l.m <ter.one.leeboi at hush.com> 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 particular the tor package which is mentioned in your ticket includes an apparmor profile and suggests apparmor-utils.
>> 
>> Also try checking your system logs
> 
> arma asked similar questions on the ticket itself:
> 
>> Comment (by arma):
>> 
>> A) Maybe it is Tor's sandbox code, misunderstanding where your
>> datadirectory is?
>> 
>> B) Maybe it is some fancy selinux thing or the like?
>> 
>> Which of those does Wheezy have?
> 
> 
> 
> Tim Wilson-Brown (teor)
> 
> teor2345 at gmail dot com
> pgp ABFED1AC
> https://gist.github.com/teor2345/d033b8ce0a99adbc89c5
> 
> teor at blah dot im
> OTR D5BE4EC2 255D7585 F3874930 DB130265 7C9EBBC7
> 
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.torproject.org/pipermail/tor-dev/attachments/20150708/eaf53671/attachment-0001.html>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: signature.asc
> Type: application/pgp-signature
> Size: 832 bytes
> Desc: Message signed with OpenPGP using GPGMail
> URL: <http://lists.torproject.org/pipermail/tor-dev/attachments/20150708/eaf53671/attachment-0001.sig>

How do I check that sandbox thing?
BTW I'm only running a bridge relay. I don't use TBB or whatever.