From: Andrey V Khavryutchenko [mailto:akhavr@compchem.kiev.ua]

Hi, Martijn!

...

...

...

...

...

"MP" == Martijn Pieters writes:

MP> Whoops! Yes, if you are wondering why tracebacks still are being MP> displayed, you are probably still running with the -D flag in your MP> start file. Remove it and enjoy the clarity of your error messages. =)

And is there way to still have tracebacks in <PRE>, but wo -D flag?

When I start Zope with -D and leave it running, closing the control terminal, it barfs with the following error:

File /usr/local/apache/zope/lib/python/Products/GenericUserFolder/User.py, line 211, in authenticate File /usr/local/apache/zope/lib/python/zLOG.py, line 198, in LOG File /usr/local/apache/zope/lib/python/Zope/ZLogger/ZLogger.py, line 18, in log_write File /usr/local/apache/zope/lib/python/Zope/ZLogger/stupidFileLogger.py, line 40, in __call__ File /usr/local/apache/zope/lib/python/Zope/ZLogger/stupidFileLogger.py, line 62, in stupid_log_write IOError: [Errno 5] Input/output error

Confirmed on FreeBSD and Linux. Zope 2.1.2

Indeed, this is caused by the fact you closed STDOUT and STDERR on the process. In stead of the -D, you can start Zope up with z2.py [options] Z_DEBUG_MODE=1 where [options] is your current list of options used minus the -D flag. Zope then will behave demonic again (run nohup) and you'll only miss out on extra log messages from ZServer. You might want to add STUPID_LOG_FILE=[path to log] as well, so that logging messages (like that of the GUF) will be sent to the proper log file. -- Martijn Pieters, Software Engineer | Digital Creations http://www.digicool.com | Creators of Zope http://www.zope.org | mailto:mj@digicool.com ICQ: 4532236 | PGP: http://wwwkeys.nl.pgp.net:11371/pks/lookup?op=get&search=0xA8A32149 -------------------------------------------