On Tue, May 12, 2009 at 11:15 PM, Boyd Stephen Smith Jr. <b...@iguanasuicide.net> wrote: > In <cfb54190905121302h695d3eb6t61f08bb9294fe...@mail.gmail.com>, Hai Zaar > wrote: >>On Tue, May 12, 2009 at 11:00 PM, Patrick Matthäi <pmatth...@debian.org> > wrote: >>> Hai Zaar schrieb: >>>> On Tue, May 12, 2009 at 10:55 PM, Patrick Matthäi >>>> <pmatth...@debian.org> >>>> wrote: >>>>>> Well... does it mean I'll have to create /var/log/dirlocks during >>>>>> boot process? If yes, is there any service in Debian that can create >>>>>> requested files/dirs on boot? (Please do not tell me that I need to >>>>>> write init script to do it :) >>>>> Wouldn't it make sense to write those lockfiles to ~/ instead of a >>>>> systemwide dir? >>>> Some tools that use libbash (my custom app for example), run scripts >>>> as system users that do not have valid ~/ >>> A valid point maybe also /tmp, your /var/lock/dirlocks has currently the >>> same functions (meant as permissions) as /tmp. >>Sure. But still I need to create /tmp/dirlocks >>on boot. How do I do it? > > I believe Patrick meant to put the files in /tmp, not in /tmp/dirlocks. If > you need the locks to last across reboots, /var/tmp, not /var/tmp/dirlocks. I need separate 1777 directory for locks library of libbash, since it may create rather complex file structure there, so I do not want to put it to just /tmp or /var/tmp/, since it may lead to collisions with files created manually by users (yes, I understand that users can occasionally, or on purpose to create files in /var/tmp/dirlocks as well, but that is another story).
-- Zaar -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org