> I'd add another requirement, not optional at all:
>
> When run as a service, svnserve should *not* register
> with the service manager and start handling svn requests.
> It should spawn another copy of itself for request handling,
> and just monitor the worker process in the service part.
> Why? Because, if the "real" server crashes, the watchdog
> can notice that and restart it. You can't persuade Windows'
> service manager to do something like that, and it would be
> nice if we didn't require an administrator's manual
> intervention in the case of a "benign" crash.
With all respect, you're wrong -- your knowledge is out of date. The
Windows SCM has excellent support for automatic service restart, and this
facility is standard, documented, and understood by Windows service
administrators. I would much, much, much rather use the existing,
documented, tested, and supported mechanism for achieving this than rolling
a service-specific one.
> FWIW, the FireDaemon service manager has similar functionality,
> with throttles to control the total number of crashes allowed
> and their frequency (e.g., if it's once a week, keep restarting
> the process; but it it's every five minutes, yell for help and
> stop).
>
> -- Brane
The Windows SCM also supports this. See the following links:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dllproc/bas
e/changeserviceconfig2.asp
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dllproc/bas
e/service_failure_actions_str.asp
-- arlie
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Feb 21 18:30:33 2006