Agreed, I don't need to restart the
service. I was just worried about packing the database, then some
time later doing something that requires a restart, like installing a product,
and having a failure at that point attributable to the pack failure.
At worst I would have to revert to the database prior to the pack. Having
been in the business for a few years and knowing Murphy's Law from direct
experience, I'm just being cautious I guess.
Scott
Why do you have to
restart Zope? I pack the database now and again (usually after a lot of
management) and never restart Zope.
J
From: "Meilicke, Scott"
<scott.meilicke@intp.com>
Date: Wed, 26 Apr 2000 13:34:54
-0700
To: "'zope@zope.org'" <zope@zope.org>
Subject:
[Zope] Database maintenance issues
Hi all,
I've had
some interesting database maintenance behavior. When I go to the
control panel, Database Management, and "Pack" items older than 100 days,
then restart zope, zope doesn't restart. python just sucks up an
entire cpu (dual cpu server, NT). If I Pack older than 5 days, and
restart, all is well and zope comes right back. Note my
database is probably about 2 months old, although it's gone through several
installations of zope, starting with 2.1.3, on linux and NT. It seems
if I Pack items older than the database, I corrupt the db some how.
I'm running 2.1.6 on NT with sp5. Any thoughts?
Thanks - Scott