I restart using ./zopect1 then start
I'm right in thinking that all you do is take out the # in the config file?On 9/22/05, Peter Bengtsson [EMAIL PROTECTED]
wrote:When you switch debug-mode on, do you start zope with ./bin/runzope ?
and if so, what are the error messages if any?2005/9/21,
I guess you actually mean ./zopectl not ./zopect1
Try ./runzope which will spit out all messages to stdout.
2005/9/22, michael nt milne [EMAIL PROTECTED]:
I restart using ./zopect1 then start
I'm right in thinking that all you do is take out the # in the config file?
On 9/22/05, Peter
Yes, that's what I mean. I'll try that.On 9/22/05, Peter Bengtsson [EMAIL PROTECTED] wrote:
I guess you actually mean ./zopectl not ./zopect1Try ./runzope which will spit out all messages to stdout.2005/9/22, michael nt milne [EMAIL PROTECTED]:
I restart using ./zopect1 then startI'm right in
michael nt milne wrote at 2005-9-21 23:34 +0100:
Has anyone had any problems running in debug mode?
A feature, I find stupid, but many (knowledgeable) people are fond of:
A Zope in debug mode will not start if any product has import
problems...
And insaner yet:
These problems are
Has anyone had any problems running in debug mode? I took out the # in the zope.conf file next to - debug-mode on which would set it to be on. However my server wouldn't come back up so I had to turn it off.
Zope Version
(Zope 2.8.0-final, python 2.3.5, linux2)
Python Version
2.3.5
When you switch debug-mode on, do you start zope with ./bin/runzope ?
and if so, what are the error messages if any?
2005/9/21, michael nt milne [EMAIL PROTECTED]:
Has anyone had any problems running in debug mode? I took out the # in the
zope.conf file next to - debug-mode on which would set
