RE: Proposed work for running svnserve as a Windows service

Well, that's reasonable. But it means that the --list-services command will
only be able to show the command line, rather than having knowledge of what
the command line means.

If this were the design choice, then there would need to be some
deterministic marker between the parameters to the --create-service command,
and the parameters to the (later) svnserve process. For example:

svnserve --create-service foo --service-start=manual --args --root ...

That, or the "--create-service <name>" pair of argv elements could be the
marker itself, and all parameters that relate to the --create-service
command could come before the --create-service:

svnserve --service-start=manual --create-service foo --root ...

-- arlie

-----Original Message-----
From: Peter Samuelson [mailto:peter@p12n.org]
Sent: Tuesday, February 21, 2006 12:59 PM
To: dev@subversion.tigris.org
Cc: Arlie Davis
Subject: Re: Proposed work for running svnserve as a Windows service

[Max Bowsher]
> > --create-service <name> --root <root> [--auto | --demand]
>
> Also, --root is not enough. --listen-host, --listen-port, and
> --read-only must also be service-specifiable.

In fact, just say that --create-service <name> takes *all* the rest of
argv[] (except for --automatic / --manual) and tells the service controller
to pass it to svnserve along with --service.

Better that than to try to anticipate the instance-specific options one
might want. New relevant options could be added in the future, too.

> > --delete-service <name> --root <root>

I agree with Max, since the service name is unique, you should just trust
that the admin typed the right one. If more argv[] *is* passed, though, you
probably should just check all of it against what is registered.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Feb 21 21:56:36 2006