A little tip for a little horror story (*NIX platforms): fuser -n tcp -ikv 8080 Fuser shows processes that use filehandles. The above options refer to a tcp filehandle (-n tcp), on port 8080. The options (k) kill all processes using this filehandle, (i) ask before killing each process, and (v) do it verbosely. Just a note: if you do this as a normal user, you will get no feedback. As root, the command works. Troy -----Original Message----- From: Dieter Maurer [mailto:dieter@handshake.de] Sent: Wednesday, January 31, 2001 2:56 PM To: zope@zope.org Cc: brian@digicool.com Subject: [Zope] Little Zope horror story Another little Zope horror story. You need to be worried only if you start external background processes from Zope. Today was not a good Zope day for me: Colleagues are currently installing a new firewall. Something went wrong and the Zope Webserver was frozen in connections with the backoffice behind the firewall. To get things start again, I stopped Zope and tried to restart it, but in vain! Zope continued to report "address already in use". Of cause, there was no longer any Zope process that used that port... After 1/2 hour of desparate search, I found the culprit. It was again an external background process. It had inherited the open listening socket and kept the port blocked. It, too, was frozen by the firewall and made no longer any progress. Killing the external process let Zope start again. The listening socket should get a "close_on_exec", too, as now do the request sockets. Dieter _______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )