[arch-general] [PATCHES] About /var/run/ and /var/lock/ checks in daemons
Gerardo Exequiel Pozzi
vmlinuz386 at yahoo.com.ar
Thu Feb 12 17:42:07 EST 2009
Jan de Groot wrote:
> On Thu, 2009-02-12 at 05:51 -0200, Gerardo Exequiel Pozzi wrote:
>> Hi people!
>> I interested to make Arch Linux suitable for use with a /var/run and
>> /var/lock that are mounted as tmpfs. But this also helps, in the case
>> that not mounted as tmpfs, to make more simple "purge function" for
>> these directories at rc.sysinit step.
>> In my case this is "just for fun!", but other users can be benefited by
>> this, for example "netbook users".
>> OK, i initially created rc-script patches for the packages in the extra
>> repo that use /var/run/program-name-directory and fails if not exists.
>> (these list was obtained with """ for x in $(find
>> /usr/share/pkgtools/lists -type f); do egrep -l "var/run/.+" $x;done """
>> @@NOTE@@: I will send the patches to the FL individualy per package now,
>> reference to this email in FL, and then copy the links to response in
>> this email. ;)
>> Please review it, thanks in advance. :)
> If this requires patching so many packages, and given the fact
> that /var/run on tmpfs is not default in archlinux, maybe you should try
> building /var/run from an initial directory or something like that. This
> is also what I use for my OpenBSD router which runs from compactflash
> and has /var mounted on ramdisk.
I know that Arch Linux don't support these directories as tmpfs or "all
empty" by default, but with these trivial patches to rc-script can
Not only this is usefull for "tmpfs", maybe for other things.
Ok the FHS recomendations, about /var/run as how to interpret the FHS's
recommendations can lead to different paths:
For example (PATH 1) if we understand that /var/run at startup must be
completely clean, these patches are useful. But (PATH 2 "The current
Arch" ) if we interpret that there should be no files, but there may be
The number of packets that need to be changed I do not think is problem,
also need not be changed immediately. Maintainers can apply the patch
for the next update when new version is released.
For example, the current rc-script of HAL that you mantain, it check
that the /var/run/hald/ and subdirs are created, but these are always
created by the package. :) Why not do the same with other packages?
Personally it is not something I need, just occurred to me that it might
be a good idea, I take my time researching what packages were needed,
and I did.
Sorry if I bothered.
Thanks for your time.
(and sorry for my bad english)
Gerardo Exequiel Pozzi ( djgera )
Key fingerprint = 0CAA D5D4 CD85 4434 A219 76ED 39AB 221B 1B8C 330D
More information about the arch-general