This should be fine.... but if you want you could delete the temp_folder object and replace it with a "dummy" object (maybe a Python Script?) with the name 'temp_folder' to cause it from being created. At least I *think* this will work. ;-) On Fri, 2002-12-13 at 14:57, Chris Muldrow wrote:
Now that I've got sessioning backed by Berkeley Storage via various howtos, my session data container lives in a Berkeley-backed folder in the root of my zope called session_storage. The default temp_folder that Zope creates is still sitting in the root of my zope with the default data container inside. Is that folder sucking down RAM and using resources, or does it just sit happily if the session data manager isn't making calls to it? I ask because it won't stay deleted if I use an external method to kill it--it returns like a bad fungus when I restart a Zope client.
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )