Here is an earlier answer that helped me with the same problem. I have a startup script that runs when the machine boots, so there is no terminal to write to: At 08:13 -0500 15.1.2002, Jens Vagelpohl wrote:

LocalFS is trying to write something to the terminal.

run your zope instance with nohup, like

[machine:~] user% nohup ./start &

this will send anything that would be written to the terminal to a text file named "nohup.out" in that same location and you can safely close the terminal window. of course it makes sense to check that file once in a while. in this case the product wants to write a traceback.

jens

I added "nohup" before my "./start" command in my startup file, and the product worked after that. So far, there have not been any tracebacks - I have no clue what LocalFS is trying to communicate.... cheers, khk ...... At 20:04 +0100 13.2.2002, Dieter Maurer wrote:

Jens-E. Hansen writes:

...

Are there any konwn issues concerning zope 2.5.0 and LocalFS? I get errors installing this product:

Traceback (most recent call last): File "/usr/local/zope/Zope-2.5.0-src/lib/python/OFS/Application.py", line 531, in import_product product=__import__(pname, global_dict, global_dict, silly) ... File "/usr/lib/python2.1/traceback.py", line 13, in _print file.write(str+terminator) IOError: [Errno 5] Input/output error You shall receive a traceback for an exception, but the current file object cannot be written. This may happen, when you start Zope in a dialog and then close this dialog...