[Checkins] [zopefoundation/nt_svcutils] f90745: Add nt_svcutils package (break out of Startup to h...
GitHub
noreply at github.com
Mon Feb 25 21:22:40 UTC 2013
Branch: refs/heads/zope2
Home: https://github.com/zopefoundation/nt_svcutils
Commit: f90745ac79823eaa55bcf3ecf50492eac3374c36
https://github.com/zopefoundation/nt_svcutils/commit/f90745ac79823eaa55bcf3ecf50492eac3374c36
Author: Chris McDonough <chrism at plope.com>
Date: 2003-08-20 (Wed, 20 Aug 2003)
Changed paths:
A __init__.py
A service.py
Log Message:
-----------
Add nt_svcutils package (break out of Startup to have a shot at using
the nt service utilities within ZEO and ZRS).
Commit: 4a12cfbd7440d2c496db43e909dc2bc4d66cf35b
https://github.com/zopefoundation/nt_svcutils/commit/4a12cfbd7440d2c496db43e909dc2bc4d66cf35b
Author: Jeremy Hylton <jeremy at svn.zope.org>
Date: 2004-01-13 (Tue, 13 Jan 2004)
Changed paths:
M service.py
Log Message:
-----------
Refactored, but untested.
Refactor the main SvcDoRun() method to make it a little easier to
read. Move the details of log messages to helper methods. Trim
comments that explain obvious code.
Make log messages read the same as zdaemon log messages.
Commit: 528def79cb5c9048ca914e84b267e0041060eb4e
https://github.com/zopefoundation/nt_svcutils/commit/528def79cb5c9048ca914e84b267e0041060eb4e
Author: Jeremy Hylton <jeremy at svn.zope.org>
Date: 2004-01-13 (Tue, 13 Jan 2004)
Changed paths:
M service.py
Log Message:
-----------
Fix problem with import.
Commit: b215a05adcfa0441a3e910a51acb071fb73a7ed2
https://github.com/zopefoundation/nt_svcutils/commit/b215a05adcfa0441a3e910a51acb071fb73a7ed2
Author: Jeremy Hylton <jeremy at svn.zope.org>
Date: 2004-01-13 (Tue, 13 Jan 2004)
Changed paths:
M service.py
Log Message:
-----------
Checkpoint of wrapper for uncoperative programs.
Adds an option to spawn a process and capture its I/O. Just a
checkpoint because it doesn't do anything with the captured I/O yet.
Commit: f0d0735184c33a34d8956f098b2253cecce1f3d1
https://github.com/zopefoundation/nt_svcutils/commit/f0d0735184c33a34d8956f098b2253cecce1f3d1
Author: Jeremy Hylton <jeremy at svn.zope.org>
Date: 2004-03-29 (Mon, 29 Mar 2004)
Changed paths:
M service.py
Log Message:
-----------
Merge jeremy-windows-service-branch to the trunk.
There are no tests for this code, but the branch was tested by using
it for releases of some Zope Corp. products.
Commit: 47146054487928006f4d11e614a24d92bfc09bee
https://github.com/zopefoundation/nt_svcutils/commit/47146054487928006f4d11e614a24d92bfc09bee
Author: root <root at svn.zope.org>
Date: 2004-05-11 (Tue, 11 May 2004)
Log Message:
-----------
Set mime-type or svn-eol property from cvs expansion data
Commit: d916ad5cdfd6c1dc8d020ef8bf227cdc15d39ecc
https://github.com/zopefoundation/nt_svcutils/commit/d916ad5cdfd6c1dc8d020ef8bf227cdc15d39ecc
Author: Sidnei da Silva <sidnei.da.silva at gmail.com>
Date: 2005-04-13 (Wed, 13 Apr 2005)
Changed paths:
M service.py
Log Message:
-----------
Major service enhancements. Service cleanly shuts down child, and if child
fails the tail of the process output (which generally contains a traceback)
is
written to the event log.
Minor tweaks to the Windows build 'clean' process and documentation tweaks.
Don't kill the service if we can't write to the event log
Commit: c9b1074d3633502ee9e97b9590f59e001635f0ec
https://github.com/zopefoundation/nt_svcutils/commit/c9b1074d3633502ee9e97b9590f59e001635f0ec
Author: Tim Peters <tim.one at comcast.net>
Date: 2005-04-19 (Tue, 19 Apr 2005)
Changed paths:
M service.py
Log Message:
-----------
Port from Zope 2.7 branch.
After consulting with Mark Hammond, removed the explicit calls to SvcStop().
That method gets invoked automatically by the services framework when a
stop request is generated. Calling it explicitly too caused the onStop()
method to get called multiple times. At least ZRS's Service subclasses
have onStop() methods that can't be called multiple times without raising
exceptions (they shut things down, and stuff like sockets go away the
first time onStop() gets called).
Commit: a288af788145edd2aa5b91ae373fba471ebac41c
https://github.com/zopefoundation/nt_svcutils/commit/a288af788145edd2aa5b91ae373fba471ebac41c
Author: Tim Peters <tim.one at comcast.net>
Date: 2005-06-08 (Wed, 08 Jun 2005)
Changed paths:
M service.py
Log Message:
-----------
Merge rev 30688 from 2.8 branch.
Import pywintypes first.
Mark Hammond's checkin comment for Zope 2.7's WinSignalHandler.py,
rev 1.1.2.2:
"""
As at pywin32-204, we must ensure pywintypes is the first win32 module
imported in our process, otherwise we can end up with 2 pywintypesxx.dll
instances in our process resulting in:
TypeError: The object is not a PySECURITY_ATTRIBUTES object
"""
Mysterious error popup boxes have also been seen, on boxes with a
pre-pywin32-204 installation leaving pywin32 DLLs in the system32
directory.
Commit: 7cf648eb04b00bd95d58f912035b9c34998ffa38
https://github.com/zopefoundation/nt_svcutils/commit/7cf648eb04b00bd95d58f912035b9c34998ffa38
Author: Tim Peters <tim.one at comcast.net>
Date: 2005-06-20 (Mon, 20 Jun 2005)
Changed paths:
M service.py
Log Message:
-----------
Merge rev 30868 from 2.8 branch.
Port from 2.7 branch.
Shut down cleanly when Windows is shutting down.
Commit: faef03b6f5d1d9906027d93584e9f55ad052f190
https://github.com/zopefoundation/nt_svcutils/commit/faef03b6f5d1d9906027d93584e9f55ad052f190
Author: Andreas Jung <yet at gmx.de>
Date: 2005-11-18 (Fri, 18 Nov 2005)
Changed paths:
M service.py
Log Message:
-----------
updated to ZPL 2.1 to be in sync with Zope 3
Commit: 61b00a1f3b519bf8034fe5a781c083b01ae33d1f
https://github.com/zopefoundation/nt_svcutils/commit/61b00a1f3b519bf8034fe5a781c083b01ae33d1f
Author: Sidnei da Silva <sidnei.da.silva at gmail.com>
Date: 2005-12-21 (Wed, 21 Dec 2005)
Changed paths:
M service.py
Log Message:
-----------
- Collector #1939: When running as a service, Zope could
potentially collect too much log output filling the NT Event
Log. When that happened, a 'print' during exception handling
would cause an IOError in the restart code causing the service
not to restart automatically.
Problem is that a service/pythonw.exe process *always* has an
invalid sys.stdout. But due to the magic of buffering, small
print statements would not fail - but once the file actually
got written to, the error happened. Never a problem when
debugging, as the process has a console, and hence a valid
stdout.
Compare: https://github.com/zopefoundation/nt_svcutils/compare/f90745ac7982^...61b00a1f3b51
More information about the checkins
mailing list