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

[intrigeri]

aexlfowley at web.de wrote (08 Jul 2015 17:57:24 GMT) :
> (Both packages for 0.2.5.12 and 0.2.6.9 contain an apparmor profile.
> Only change and new line is
>   /usr/bin/obfs4proxy PUx,
> in /etc/apparmor.d/abstracions/tor)

FTR, the systemd unit file in Debian sid's 0.2.6.9-1 doesn't enable
the AppArmor profile (yet), so I doubt AppArmor has anything to do
with this problem (aa-status will tell you).

However, it has:

  PrivateTmp=yes
  PrivateDevices=yes
  ProtectHome=yes
  ProtectSystem=full
  ReadOnlyDirectories=/
  ReadWriteDirectories=-/var/lib/tor
  ReadWriteDirectories=-/var/log/tor
  ReadWriteDirectories=-/var/run

... which explains why /media/cRAID/Tor/lock isn't writable.

So you'll want to add what is called a "drop-in override file" in
systemd's terminology (that can be created e.g. with `systemctl
edit'), that adds a ReadWriteDirectories= directive pointing to the
directory you want.

Cheers,
--
intrigeri