Hi, On Tue, Jan 26, 2016 at 10:07:18PM +0200, Samuli Seppänen wrote: > One question, primarily to Heiko... does the interactive service solve > the use-case where the administrator/user wants to have persistent > connections that come up on boot and are not closed or managed in any > way in the meantime? In this use-case no user interaction is wanted, > needed or expected.
As far as I understand, the interactive service is fully controlled by
the GUI ("hey service, run *this* with my credentials, but permit it
to talk to you and request route changes").
The "openvpnserv.exe" process can now actually run as two different
things - the classic "openvpn service" which just starts openvpn.exe
at service start time, and the new "interactive service" which helps
the GUI for, well, "interactive" openvpn usage.
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"?
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
signature.asc
Description: PGP signature
