> 1) that'll clear out the template cache as well, won't it? wouldn't > it be better to do ./data/cache ./data/sessions
Good point. Thanks. > 2) i've never used bdb as a backend for this; but wouldn't removing > bdb files corrupt the bdb index ? wouldn't it be safer to run an app > that loop's through all the bdb entries and deletes old ones ? the > solution you're looking at looks like the right one for flat-file / > pickled / yaml session manager... not bdb. at least to me! That's what I'm trying to figure out - cache actually only has 14 files in it vs the 200k in sessions... Another alternative is to use memcached as a backend, that'll prune out all the old entries once it runs out of space. There is the potential of this canning sessions too early however if there is not enough memory to store all the entries, which is why i've been using bdb till now. I guess another option would be to use postgres or mysql as a backend, but iirc this also requires some manual pruning of old sessions. Wrt flat file/yaml - can that be used with beaker? Are there any advantages/disadvantages? Damain -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
