Greetings; Was reading up on zope labs on who to use cron and wget to call zope functions and Im almost there. What I would like to do is set a cron job to pack the db and flush the cache on a regular basis. Using the following URL on a test machine I can get there almost; http://XXXXX:xxxx@localhost:8181/Control_Panel/Database/manage_cacheGC but I am at a loss on how to activate the 'minimize' function as I dont know how to call it. Same scenario for 'pack' in ~/Database/manage Any clues would be greatly appreciated, or direction towards some docs on an alternative way of routinely packing the db and cleaning the cache.. Best and many thanks /ch
You don't need to do this via wget. There is a utilities (down in ~lib/python/ZODB/ ?) called fsrecover.py that has an option to pack the database. fsrecover.py + cron = packed ZODB. Enjoy. Jake -- http://www.ZopeZone.com Chris Herrnberger said:
Greetings;
Was reading up on zope labs on who to use cron and wget to call zope functions and Im almost there.
What I would like to do is set a cron job to pack the db and flush the cache on a regular basis. Using the following URL on a test machine I can get there almost;
http://XXXXX:xxxx@localhost:8181/Control_Panel/Database/manage_cacheGC
but I am at a loss on how to activate the 'minimize' function as I dont know how to call it. Same scenario for 'pack' in ~/Database/manage
Any clues would be greatly appreciated, or direction towards some docs on an alternative way of routinely packing the db and cleaning the cache..
Best and many thanks
/ch
_______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
On Tuesday 11 November 2003 14:21, Jake (aka BZ) wrote:
You don't need to do this via wget.
There is a utilities (down in ~lib/python/ZODB/ ?) called fsrecover.py that has an option to pack the database.
fsrecover.py + cron = packed ZODB.
Ah many thanks Jake. Any clues on how to flush the cache on regular basis, then this maitenance item would be all covered..:) /ch
You don't need to do this via wget.
There is a utilities (down in ~lib/python/ZODB/ ?) called fsrecover.py that has an option to pack the database.
fsrecover.py + cron = packed ZODB.
Ah many thanks Jake. Any clues on how to flush the cache on regular basis, then this maitenance item would be all covered..:)
Look at the source of the ZMI page that does this and you'll be able to see the URL that you need to poke. But I don't see the sense in flushing the cache: it doesn't grow once it's full and a cache works better when it's full. Stale data should take care of itself. --jcc -- "Code generators follow the 80/20 rule. They solve most of the problems, but not all of the problems. There are always features and edge cases that will need hand-coding. Even if code generation could build 100 percent of the application, there will still be an endless supply of boring meetings about feature design." (http://www.devx.com/java/editorial/15511)
Yeah... the cache is ok. 2.6.2 also deals a lot better with keeping the cache clean and dumping old memory. Just remember that setting the cache number will keep that amount of object per thread. Jake -- http://www.ZopeZone.com J Cameron Cooper said:
You don't need to do this via wget.
There is a utilities (down in ~lib/python/ZODB/ ?) called fsrecover.py that has an option to pack the database.
fsrecover.py + cron = packed ZODB.
Ah many thanks Jake. Any clues on how to flush the cache on regular basis, then this maitenance item would be all covered..:)
Look at the source of the ZMI page that does this and you'll be able to see the URL that you need to poke.
But I don't see the sense in flushing the cache: it doesn't grow once it's full and a cache works better when it's full. Stale data should take care of itself.
--jcc
-- "Code generators follow the 80/20 rule. They solve most of the problems, but not all of the problems. There are always features and edge cases that will need hand-coding. Even if code generation could build 100 percent of the application, there will still be an endless supply of boring meetings about feature design." (http://www.devx.com/java/editorial/15511)
_______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
On Wednesday 12 November 2003 08:15, Jake (aka BZ) wrote:
Yeah... the cache is ok. 2.6.2 also deals a lot better with keeping the cache clean and dumping old memory.
Just remember that setting the cache number will keep that amount of object per thread.
Thanks all, much to learn here, but its most interesting stuff. tks./ch
On Tuesday 11 November 2003 14:21, Jake (aka BZ) wrote:
There is a utilities (down in ~lib/python/ZODB/ ?) called fsrecover.py that has an option to pack the database.
On my 2.6.2 test install, there is also fspack.py which I presume is preferable over fsrecover.py for simply packing the db? /ch
Now, I really hope this is the right mailing list to send this (newbie) kind of question to. A client have a Zope installation (ver. 1.10.3). Now, this installation seems to be, eh, a far bit obsolete. I have no idea why, but even the simplest things that should have worked (while coding DTML) doesnt. Thus, I have installed Zope 2.6 (latest version right) on my Win32 workstation here... I would really have liked to be able to get the client application made in 1.10.3 to work on 2.6. I did a futile attempt on exporting and importing, but eh - even the Zope newbie me figured that only magic could make that happen... Is there anyone with a good clue of how to export from 1.10.3 (i.e. "export.bbe") to this new version? Best regards Robert. ----- Original Message ----- From: "Chris Herrnberger" <chris123@magma.ca> To: <jake@zopezone.com> Cc: <zope@zope.org> Sent: Tuesday, November 11, 2003 5:41 PM Subject: Re: [Zope] cron
On Tuesday 11 November 2003 14:21, Jake (aka BZ) wrote:
There is a utilities (down in ~lib/python/ZODB/ ?) called fsrecover.py that has an option to pack the database.
On my 2.6.2 test install, there is also fspack.py which I presume is preferable over fsrecover.py for simply packing the db?
/ch
_______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
On Tue, Nov 11, 2003 at 05:54:16PM -0200, Robert Restad wrote:
Now, I really hope this is the right mailing list to send this (newbie) kind of question to.
A client have a Zope installation (ver. 1.10.3). Now, this installation seems to be, eh, a far bit obsolete.
understatement :-)
I have no idea why, but even the simplest things that should have worked (while coding DTML) doesnt.
well, an awful lot has changed since 1.x. I don't know when the <dtml-var foo> syntax was introduced, but there was an older syntax used in 1.x. Heck, I've been working with zope since 1999 and we were already on 2.x then.
Thus, I have installed Zope 2.6 (latest version right) on my Win32 workstation here... I would really have liked to be able to get the client application made in 1.10.3 to work on 2.6. I did a futile attempt on exporting and importing, but eh - even the Zope newbie me figured that only magic could make that happen...
Is there anyone with a good clue of how to export from 1.10.3 (i.e. "export.bbe") to this new version?
You may have to move incrementally - first get to 2.0, then 2.2, then you should be in good shape to go current. All old zope releases are here: http://zope.org/Products/Zope Check the doc/CHANGES.txt that comes with the source releases, there may be relevant notes there. At the very least you will need this: http://www.zope.org/Products/Zope/2.2.0/upgrading_to_220 -- Paul Winkler http://www.slinkp.com Look! Up in the sky! It's BASHER META WATER! (random hero from isometric.spaceninja.com)
Sounds good... (I am not sitting at a machine I can see all the utilities). Google found: http://www.zope.org/Members/fritz/howto_compress_datafs_using_cron http://people.enginesofcreation.ie/mick/archives/000027.html But I still think the utility is the best option. As a note, since Packing the ZODB is a pretty "serious" thing, you might want to make sure you have a good backup beyond the backup that Zope makes before packing it. For me, I pack that database when I am A) sure there is little traffic and B) I can get to and recover it quickly if something goes wrong. Jake -- http://www.ZopeZone.com Chris Herrnberger said:
On Tuesday 11 November 2003 14:21, Jake (aka BZ) wrote:
There is a utilities (down in ~lib/python/ZODB/ ?) called fsrecover.py that has an option to pack the database.
On my 2.6.2 test install, there is also fspack.py which I presume is preferable over fsrecover.py for simply packing the db?
/ch
On Tuesday 11 November 2003 14:59, Jake (aka BZ) wrote:
Sounds good... (I am not sitting at a machine I can see all the utilities).
Google found: http://www.zope.org/Members/fritz/howto_compress_datafs_using_cron http://people.enginesofcreation.ie/mick/archives/000027.html
Poifect...;) With gratitude. /ch
participants (5)
-
Chris Herrnberger -
J Cameron Cooper -
Jake (aka BZ) -
Paul Winkler -
Robert Restad