On Tue, Jan 26, 2016 at 4:24 PM, Gert Doering <g...@greenie.muc.de> wrote:
> Since Heiko has reworked the "classic" code (in automatic.c now, as > he called this "automatic service") maybe we can just use the opportunity > to get the remaining issues fixed - is there more than "restart openvpn.exe > when it dies"? > Haven't look at the new code, but of if the "automatic service" logic is the same as before, it would take some work to make it behave like a watchdog of openvpn.exe processes. Using NSSM for "automatic" uses and this one only for interactive start ups by the GUI may be a better option. NSSM has the added advantage of one service per config which could be independently stopped and restarted etc. The original service starts all the configs and then sits there waiting for the exit event to trigger, at which point the service will just stop. For one, the exit event will not trigger when openvpn.exe quits and even if we make the event to trigger, there is only one common event for multiple configs, and the service just stopping at such an event serves no purpose. Instead of fixing it why not just use NSSM? Then the interactive service patch could be decoupled from openvpnserv and provided as a new feature independent of the original service. Selva
