-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dieter Maurer wrote: | Tres Seaver wrote at 2005-3-9 16:24 -0500: | |>... |> 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. | | We usually start Zope with "bin/zopectl start" (because consoles are | not garanteed to remain open). And then you see nothing, when there | are problems during startup. When debugging a starup problem, I always start the appserver in the foreground, with debug-mode turned on; I then Ctrl-C to kill the foreground process (once it *does* start) and restart it in the background. The only glitch I see in this approach is that I think starting Zope in the foreground (via 'zopectl fg') should automatically turn on debug-mode; then I wouldn't need to edit zope.conf, and then re-edit it when done. 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 iD8DBQFCMKGNGqWXf00rNCgRAo72AJ9OE5GKFUL3nBfymAcyt0hzX8L+KACeMxQm PYTXEm+9jaTnarzXP/WFrUA= =ROiM -----END PGP SIGNATURE-----