Collector 1788: runzeo fails in 2.8

A patch from Mark Hammond to repair a new Windows-specific
gimmick in ZEOServer.setup_win32_signals().

NEWS.txt

-What's new in ZODB3 3.4a9?
+What's new in ZODB3 3.4b1?
 ==========================
-Release date: 12-May-2005
+Release date: DD-May-2005
 
 What follows is combined news from the "internal releases" (to support
 ongoing Zope 2.8 and Zope3 development) since the last public ZODB 3.4
 release.  These are the dates of the internal releases:
 
+- 3.4b1 NN-May-2005
 - 3.4a9 12-May-2005
 - 3.4a8 09-May-2005
 - 3.4a7 06-May-2005
@@ -100,6 +101,8 @@ ZEO on Windows
 
 Thanks to Mark Hammond for these ``runzeo.py`` enhancements on Windows:
 
+- (3.4b1) Collector 1788:  Repair one of the new features below.
+
 - (3.4a4) A pid file (containing the process id as a decimal string) is
   created now for a ZEO server started via ``runzeo.py``.  External programs
   can read the pid from this file and derive a "signal name" used in a new

src/ZEO/runzeo.py

@@ -225,10 +225,8 @@ class ZEOServer:
                                           windows_shutdown_handler)
             SignalHandler.registerHandler(signal.SIGINT,
                                           windows_shutdown_handler)
-            # Can use the log rotate handler too.
-            from Signals.Signals import logfileRotateHandler
             SIGUSR2 = 12 # not in signal module on Windows.
-            SignalHandler.registerHandler(SIGUSR2, logfileRotateHandler)
+            SignalHandler.registerHandler(SIGUSR2, self.handle_sigusr2)
 
     def create_server(self):
         from ZEO.StorageServer import StorageServer