I saw few cases when openvpn.exe remains running even after openvpn-gui
told it to stop (and it was awful).
is iservice magic of start/stop openvpn.exe  the same as for openvpn-gui ?

if yes, I would say that it is ok to switch to iservice by default.

2016-02-08 12:42 GMT+05:00 Gert Doering <g...@greenie.muc.de>:

> Hi,
>
> On Mon, Feb 08, 2016 at 08:35:54AM +0500, ???????? ?????????????? wrote:
> > I have one question regarding that.
> > when we deployed openvpn, we used to supply our users a config file
> without
> > "nobind" keyword.
> >
> > it worked for most of our users, however, those who needed 2 or more vpn
> > connections complained that "port already bind". so, we added "nobind" to
> > client config files and people become happy.
> >
> > what about that PR. there might be cases when
> >
> > 1) interactive service installed
> > 2) user is administrator
> >
> > how many openvpn processes will be running ? how many of them will
> attempt
> > to bind to 1194 ?
>
> You still seem to misunderstand what iservice does - iservice does not
> automatically run "thousands of OpenVPN processes".  It will do what the
> GUI tells it to.
>
> So if it does not work without iservice because GUI tries to start two
> jobs with "bind 1194", it will not work with iservice either - no
> difference here.  First bind will succeed, second one will not.
>
> What is "first" depends on what the GUI starts first - it's all controlled
> by the GUI, the service does not start anything on its own.
>
> 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
>

Reply via email to