fritz, packing works very well from any of the connected ZEO clients. what probably throws you off is that when you hit "pack" the page comes back immediately and there is no visible change. packing is being initiated and you will see results after a while (the while being longer the larger your Data.fs is) by looking at the contents of the directory where your Data.fs is. you'll see a new file, Data.fs.pack, that is being built and when it is finished the old Data.fs gets renamed to Data.fs.old while Data.fs.pack becomes Data.fs. this process can take quite some time and the management interface in your ZEO client will only show the new database size after Data.fs.pack has been put in place of Data.fs. if you have problems with the 2GB file size limit i suggest (if you're on linux) that you go with a kernel that can handle large files (i have a test rig that uses a 2.2.17 kernel) and hand-compile python to enable large file support. jens On Thursday, August 16, 2001, at 05:42 , Fritz Mesedilla wrote:
I'm sorry but I am really getting irritated with the 2GB limit!
Data.fs packing also doesn't work while zeo is running.
How can I pack Data.fs without turning zeo off? It doesn't work in the Management Screen.
The management screen for the zeo server is also connecting to it like it is a remote server. Is this the problem? But when I try to start zope without activating the custom_zodb.py, it won't start. I have to make zope think it is trying to connect to a different server.
Please help me!
Fritz Mesedilla