On Tuesday 20 October 2015 10:15:22 Samuli Seppänen wrote:
Are you saying that the interactive service also doubles as a Windows
system service? If so, can it be configured to autostart selected
openvpn connections on boot and restart them if they crash/stop?
No, and I do not think that the service should take care of that. That's
rather things that can be handled by the GUI.
What about persistent connections, especially on Windows servers?
The interactive service patch doesn't remove the currently available service.
So, you still can fire up any connections the way it was before. I personally
do not care about the original service though, it may very well be that it
lacks decent functionality.
The original openvpnserv.exe is truly crappy. It will not quit if all
connections have died. It will not restart a connection should it crash.
A single non-functional OpenVPN connection prevents it from launching
the others (afaik). It will not work on Windows 10 in any reasonable
fashion and works badly on anything post-Windows 7. It also does not
handle resuming from suspend/hibernate properly.
My NSSM-based replacement thingie aims to address all these
shortcomings. I believe the interactive service and NSSM are complementary.
--
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc
irc freenode net: mattock
