-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Bert Vanderbauwhede wrote: | On Tue, 8 Mar 2005 19:57:47 +0100, Dieter Maurer <dieter@handshake.de> wrote: | |>Bert Vanderbauwhede wrote at 2005-3-8 14:08 +0100: |> |>>... |>>Whenever I install |>>a product with errors Zope crashes (ie. zoperun throws an exception, shows a |>>traceback and stops, zopectl tries to restart Zope every few seconds). |>>Zope 2.6.4 |>>would start as usual, and show an error message in the Products screen. |>> |>>Is this the normal behaviour in 2.7.4? If so, why? |> |>I, too, would like to know that... |>In my view it is completely stupid! |>Especially, combined with the stupid logging behaviour |>during startup that causes error reports during this phase |>to be lost! | | | Adding "debug-mode off" to the zope configuration file works. So it is | related to the | debug mode. But crashing without writing the details to the event log | isn't what I would expect from a debug mode. That isn't what I see: when I try to start Zope for debugging ('debug-mode on' in zope.conf, running 'zopectl foreground') with a broken product, I see the traceback from the broken product on the console. In production mode, the startup code just logs the fact of the broken product and continues the startup. Tres. - -- =============================================================== Tres Seaver tseaver@zope.com Zope Corporation "Zope Dealers" http://www.zope.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCL2mJGqWXf00rNCgRAk/rAJ4ivigpGVWvdClpBe7bn3Tn6nMsCwCgj+Ta qv+rv9AKzr4HGSmaybm/hv4= =n/SU -----END PGP SIGNATURE-----