Opened 4 years ago

Last modified 15 months ago

#129 new Feature Wish

openvpnserv.exe should restart missing openvpn.exe processes

Reported by: bwess Owned by:
Priority: minor Milestone: release 2.4
Component: Generic / unclassified Version: git master branch
Severity: Not set (if unsure, select this one) Keywords: windows openvpnserv
Cc: d12fk


GUIs for the OpenVPN client increasingly use the management interface. On Windows, in setups where users are unprivileged and OpenVPN processes are started by the service wrapper GUIs have to rely on the OpenVPN processes not exiting to control and continue reusing them for many connections, but this can happen in certain cases.
The OpenVPN service wrapper should either e.g. check for the presence of management/management-hold in configuration files or have e.g. a registry entry to have it restart the missing OpenVPN processes or even let this be the default behavior (is there a case where the current behavior makes sense?).

Change History (4)

comment:1 Changed 4 years ago by bwess

This could make the behavior discussed in unnecessary or could fall back to it if there is only one configuration file (relying on Windows to do service auto-restart-after-crash does seem like an ugly hack to achieve what the service wrapper should do itself).

comment:2 Changed 20 months ago by samuli

  • Keywords windows openvpnserv added
  • Version changed from 2.2.0 to git master branch

No changes have been made to openvpnserv.exe code in ages, so this issue persists.

comment:3 Changed 15 months ago by cron2

  • Type changed from Bug / Defect to Feature Wish

Unless someone provides an actual patch for openvpnserv to do that, I think this will not be changed.

2.4 will have the new interactive service, which is MUCH better suited for working together with the Gui process (and also more secure because openvpn.exe will not need to run with admin or system privileges).

comment:4 Changed 15 months ago by cron2

  • Cc d12fk added
  • Milestone set to release 2.4

milestone set, so we can come back here at 2.4 release and verify that the interactive service is in, the documentation is clear enough, and then close it.

Note: See TracTickets for help on using tickets.