This probably means you've run Zope from a terminal but you've run it in such a way that it detaches from the terminal (e.g. not in debug mode). An answer is to run it under "nohup" which writes output to a file. This is a Zope bug that is fixed in the current trunk. On Tue, 2002-08-06 at 22:20, Robert Thomson wrote:
Just recently my Zope instance started giving IOErrors when using "print" from a custom Product.. we've been using print for debugging purposes and up until now, this has worked well..
It doesn't IOError every time, though.. in fact, it appears to only IOError every second time when it hits print... so a page reload will succeed.
At the moment I'm baffled, and am assuming it's a strange zope occurance which I hope someone else has encountered before, and solved.
Zope version is 2.5.0.
Cheers, Rob
-- Your mistakes are the only thing you'll ever truly own. Everything else someone will take credit for.
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )