Hi,
On Wed, Dec 28, 2016 at 2:37 PM, Christian Hesse <l...@eworm.de> wrote:
>
> For informational purpose we could add even more calls. That would allow to
> set intermediate status message, something like: "Up and running, currently
> serving 25 client connections."
If the daemon has to send specially crafted messages to systemd there is no
end to it. Arguably, we should also register as an event provider and send
event logs to Windows and whatever the equivalent be on OS X etc...
A cleaner approach would be to leverage on the existing management
interface and use standalone modules to do a translation between the
management and systemd/launchd//whatever. We already have the status and
progress info sent to the management interface. Just as windows GUI uses
the management interface we could somehow have an external connector from
mgmt to systemd and keep such systemd specific stuff out of openvpn.
Selva
P.S.
I am not a fan of systemd so the above is partly colored by my dislike for
it.. (it has done several extremely bad things to me in the past including
uninstalling zfs modules on update on a system which had zfs on root and no
rescue disk.. well partly my fault..)
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel
