On Thu, 10 Nov 2005, Kari Pahula wrote:
> Hello. I'm in the progress of packaging preload for Debian. There's
> one detail I'd like to discuss with you.
> Namely the /var/preload/preload.state file. FHS really frowns upon
> creating directories under /var.
In CVS, I've already moved that into /var/lib/preload.
> > Applications must generally not add directories to the top level of
> > /var. Such directories should only be added if they have some
> > system-wide implication, and in consultation with the FHS mailing
> > list.
> However, there is a place where this file would fit better,
Not sure. This is not really cache, it's more like your MySQL
database rather than manpage cache.
> > /var/cache : Application cache data
> > Purpose
> > /var/cache is intended for cached data from applications. Such data is
> > locally generated as a result of time-consuming I/O or
> > calculation. The application must be able to regenerate or restore the
> > data. Unlike /var/spool, the cached files can be deleted without data
> > loss. The data must remain valid between invocations of the
> > application and rebooting the system.
> > Files located under /var/cache may be expired in an application
> > specific manner, by the system administrator, or both. The application
> > must always be able to recover from manual deletion of these files
> > (generally because of a disk space shortage). No other requirements
> > are made on the data format of the cache directories."
> Also, it seems that preload won't gracefully recreate preload.state
> file if it is missing (required from files under /var/cache).
> SF.Net email is sponsored by:
> Tame your development challenges with Apache's Geronimo App Server. Download
> it for free - -and be entered to win a 42" plasma tv or your very own
> Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
> preload-devel mailing list
"Commandment Three says Do Not Kill, Amendment Two says Blood Will Spill"
-- Dan Bern, "New American Language"