"Arlie Davis" <adavis@stonestreetone.com> wrote on 02/21/2006 12:34:10 PM:
> Summary
> -------
>
> svnserve would be modified to add support for running "natively"
> as a Windows service. This allows svnserve to be managed like
> any other Windows service (start / stop from "Services"
> management tool, see status, manage it remotely, etc.), to be
> reliably started when the system boots, and to be reliably
> stopped when the system shuts down.
>
> Support will be provided for installing, enumerating, and
> uninstalling instances of svnserve services. The
> implementation would support any number of svnserve
> repositories; there will not be any limitation on the
> number of installed services.
I apologize in advance if this has been already discussed, but why
wouldn't you put the "service maintenance" options (create, update,
delete, list) in a separate executable, like svnservice.exe or something?
And just limit the changes to svnserve.exe to those needed to actually run
as a service? That seems like it would be a lot cleaner and greatly
reduce the changes need to svnserve.exe itself. I do not like the idea of
all of those command line options being added to svnserve.exe.
svnservice.exe could also just be a GUI with command line option support
if you were to go in this direction and then there would be less pieces to
deal with.
Thanks
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Feb 21 22:04:56 2006