On Sat, 27 May 2017 08:13:02 +0200,
J.O. Aho actually wrote:

I just doubleclick on any desired *.ovpn openvpn text file and that's all I
ever do. That puts me on VPN. There is no GUI involved.

Use "killall -9 openvpnd" and it would take care of the daemon. Sure you
can use a desktop icon for doing that.

I had to enable Telnet on Windows so is "killall" the same kind of problem
on Windows as Telnet was?

cmd\ killall
No such file or directory on Windows XP or on Windows 10

It's interesting that you recommended "killall" for Windows because there is
only one minor problem in WindowsXP and two minor problems with Windows 10
with my use model, one of each is related to killing the process.

The minor problem in both is that out of any given dozen freely available
openvpn *.ovpn configuration files to free public VPN servers, not all work.

So what happens is:
1. I group select and group "open" 10 *.ovpn files in the OpenVPN Daemon.
1. If 0 work I end up having 10 OpenVPN daemon runninglog files to close.
2. If 4 work I end up having to close 6 OpenVPN daemon runninglog files.

What happens is that the first successful connection wins, and any
subsequent successful connects automatically close (which is perfect!).

So I'm only left with the 1 (first) successful connection, with the rest
being connections which never stood a chance of being successful.

To make it easier to close the 6 remaining unsuccessful OpenVPN Daemon
runninglog files, I have them set to open in the same location so that the
[X] corner is easier to (1)click, (2)click, (3)click, (4)click, (5)click, &
(6)click.

If there was a way to close all the open unsuccessful windows, that would
make the use model even more efficient than it is now.