For development, it's better to run Zope under a DOS box by using
"runzope.bat" than it is to continually stop and start the Zope NT
service. Zope as an NT service has particularly poor error reporting
for startup problems ( see http://zope.org/Collectors/Zope/1020 ).
If you use "runzope.bat" instead of the service starter, you can visit
the "error_log" object in the ZMI, check "copy exceptions to event log",
save that, put the following in your zope.conf:
Then restart Zope.
This will cause Zope's event log to log to not only a logfile but to the
console under which you start Zope, making it easy to spot startup
errors when you use "runzope.bat".
On Tue, 2004-06-01 at 14:03, Marshall Powers wrote:
> I'm somewhat new to zope in general, and I've been having some trouble
> developing products. Im running 2.7 on WinXP as a windows service. My
> biggest problem is with debugging my products. Right now, the only
> feedback I get is whether or not the zope service starts successfully.
> It would really help if I could get some error message as to what part
> of my product zope choked on. Any Ideas?
> Thank You,
> Zope-Dev maillist - [EMAIL PROTECTED]
> ** No cross posts or HTML encoding! **
> (Related lists -
> http://mail.zope.org/mailman/listinfo/zope )
Zope-Dev maillist - [EMAIL PROTECTED]
** No cross posts or HTML encoding! **
(Related lists -