On Fri, 4 Jul 2008, Jon Peatfield wrote:
On Fri, 4 Jul 2008, Stephan Wiesand wrote:
On Fri, 4 Jul 2008, Jon Peatfield wrote:
<snip>
We do it mostly to set a few defaults (like home pages etc), but we could
proably live without it for a while if we understood what else has
changed... :-)
And we do it mostly to ban the cache from the users' home directories. To
avoid 50MB/user being occupied by cached web pages in their home
directories and on our backup tapes.
Hmm, hadn't thought of that. We used to force the cache size down low but
not the location. Maybe moving it into a suitable tmp (or tmp-like) place
would actually work. That sounds like a very good idea, I must steal it at
once!!
I suppose you need a different Cache directory for each active profile or the
browsers will corrupt things. How do you arrange that?
we have this in the .cfg:
// this file must start with // ...
var env_user = getenv("USER");
lockPref("browser.cache.disk.parent_directory","/tmp/.ffcache-"+env_user);
--
Stephan Wiesand
DESY - DV -
Platanenallee 6
15738 Zeuthen, Germany
