On Thu, 19 Aug 2010, Bastian Blank wrote:
> Package: tor
> Version: 0.2.1.26-1
> Severity: important
>
> tor writes it lock file into /var/lib, not /var/lock as mandated by the
> FHS.
>
> | # lsof -p 1440
> | [...]
> | tor 1440 debian-tor 8w REG 202,0 2003 49198
> /var/log/tor/log
> | tor 1440 debian-tor 9uW REG 202,0 0 53095
> /var/lib/tor/lock
Thanks for your report. I'm not quire sure I do agree with the problem
statement here however:
Firstly, /var/lock/, as specified in the FHS, seems to be awfully
specific to device files (which live in /dev where other kinds of
locking might be hard), and even goes so far as to mandate a special
format for the content of the lockfiles. In short, I'm not sure
/var/lock is the place for lockfiles of our kind. Can you elaborate why
you think different?
Secondly, the purpose of the lockfile is to protect the datadirectory,
which is /var/lib/tor for the default tor. As such, placing the lock
there does make a certain amount of sense - users can run other tors,
with different datadirs and then those datadirs would be protected by
their own locks.
Is there any specific problem, real or hypothetic, with having that file
be in /var/lib/tor?
Cheers,
weasel
--
| .''`. ** Debian GNU/Linux **
Peter Palfrader | : :' : The universal
http://www.palfrader.org/ | `. `' Operating System
| `- http://www.debian.org/
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
