Re: Huge cache dirs in $HOME
* Pierre THIERRY [EMAIL PROTECTED] [070314 07:51]: I just discovered today that some packages can store pretty huge cache data in my $HOME, and found that rather problematic. When I backup my home, I don't want to waste backup space or time to do it, because I have to check what eats space and tell if it's cache data. In my eyes no program at all should store caches in $HOME. There is $TMPDIR for that. Even small files can be a big problem, if you have several hundred users. I'm always collecting information how to tell programs not to do so. Mozilla derived programs normaly can be told with a pref(browser.cache.disk.capacity, 0); in the right file to globally switch it off. Against those grotesque .fonts.cache-1 files (which are not only cache that should not be in /home, but also system dependent thus even more do not belong there) running fc-cache as root on all hosts regulary helps. Hochachtungsvoll, Bernhard R. Link -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Huge cache dirs in $HOME
On Wed, 14 Mar 2007, Bernhard R. Link wrote: * Pierre THIERRY [EMAIL PROTECTED] [070314 07:51]: I just discovered today that some packages can store pretty huge cache data in my $HOME, and found that rather problematic. When I backup my home, I don't want to waste backup space or time to do it, because I have to check what eats space and tell if it's cache data. In my eyes no program at all should store caches in $HOME. There is $TMPDIR for that. Even small files can be a big problem, if you have several hundred users. Cache files which need to persist beyond the lifetime of a program can't be sanely stored in TMPDIR.[1] Since the user is running it, HOME is the most appropriate location for this type of cache, although it should be configurable if your idea of appropriateness differs. Don Armstrong 1: Or at least, not directly stored in TMPDIR without a symlink or a database somewhere. -- I'd sign up in a hot second for any cellular company whose motto was: We're less horrible than a root canal with a cold chisel. -- Cory Doctorow http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Huge cache dirs in $HOME
On Wed, Mar 14, 2007, Pierre THIERRY wrote: I just discovered today that some packages can store pretty huge cache data in my $HOME, and found that rather problematic. When I backup my home, I don't want to waste backup space or time to do it, because I have to check what eats space and tell if it's cache data. Couldn't such packages, like beagle and tracker, just use the standard directory for that purpose, like specified in XDG's basedir? FYI, There was a (underused and rather clumsy) freedesktop proposal to tell backup utilities not to backup cache files: http://lists.freedesktop.org/archives/xdg/2004-August/004306.html -- Sam. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Huge cache dirs in $HOME
Le mercredi 14 mars 2007 à 09:45 +0100, Bernhard R. Link a écrit : Against those grotesque .fonts.cache-1 files (which are not only cache that should not be in /home, but also system dependent thus even more do not belong there) running fc-cache as root on all hosts regulary helps. The system font cache is now located in /var/cache/fontconfig. The user font cache is for fonts in ~/.fonts, and I fail to see why it should be outside ~. -- .''`. : :' : We are debian.org. Lower your prices, surrender your code. `. `' We will add your hardware and software distinctiveness to `-our own. Resistance is futile.
Re: Huge cache dirs in $HOME
On Wednesday 14 March 2007, Josselin Mouette wrote: Le mercredi 14 mars 2007 à 09:45 +0100, Bernhard R. Link a écrit : Against those grotesque .fonts.cache-1 files (which are not only cache that should not be in /home, but also system dependent thus even more do not belong there) running fc-cache as root on all hosts regulary helps. The system font cache is now located in /var/cache/fontconfig. The user font cache is for fonts in ~/.fonts, and I fail to see why it should be outside ~. the original suggestion was to have everything follow the freedesktop basedir spec for the caching location, note that this spec defaults to the location $HOME/.cache (or whatever the $XDG_CACHE_HOME env var points to) -- Cheers, cobaco (aka Bart Cornelis) pgpGpQZ9csTYU.pgp Description: PGP signature
Re: Huge cache dirs in $HOME
On Wed, Mar 14, 2007 at 09:45:08AM +0100, Bernhard R. Link wrote: In my eyes no program at all should store caches in $HOME. There is $TMPDIR for that. Even small files can be a big problem, if you have several hundred users. But if TMPDIR=$HOME/tmp then you have the same problem. Furthermode, you _do want_ to store index databases unser $HOME if you are using NFS otherwise you'd have to re-index your home directory every time you sit down at a different lab machine, which would mean a huge amount of completely unneccessary extra I/O for your NFS server. Gabor -- - MTA SZTAKI Computer and Automation Research Institute Hungarian Academy of Sciences - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
