Hi, On Thu, Feb 11, 2016 at 01:14:05PM -0500, Selva Nair wrote: > (ii) openvpnserv.exe --start interactive > > Do not start the automatic service by default as that is meant for expert > users. Else it will spawn-up openvpn.exe for all configs found and possibly > mess-up with interactive use.
Right.
Maybe even change the "openvpnvsrv.exe --install" command to require
"--install interactive / --install automatic" and even *install* only
the iservice by default.
> > Given that OpenVPNService and OpenVPNServiceInteractive have been
> > separated, replacing the non-interactive variant with openvpnserv2
> > should not be too difficult.
>
> While the two services can be independently stopped and started the two are
> installed and removed together:
> openvpnserv.exe --install sets up two
> services OpenVPNService and OpenVPNServiceInteractive. So any replacement
> will have to use a name distinct from those. I think openvpnserv2 uses the
> same name "OpenVPNService" which will cause a conflict.
>
> In the long run it may be better to remove the automatic service completely
> from the openvpnsev.exe code.
I'm not going to disagree, but this should happen somewhat coordinated with
inclusion of openvpnserv2 in the installers & "an appropriate" git repo.
thanks,
gert
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany g...@greenie.muc.de
fax: +49-89-35655025 g...@net.informatik.tu-muenchen.de
signature.asc
Description: PGP signature
