Systemd service not configured to restart on failure

This forum is for admins who are looking to build or expand their OpenVPN setup.
Forum rules
Please use the [oconf] BB tag for openvpn Configurations. See viewtopic.php?f=30&t=21589 for an example.
Post Reply
OpenVpn Newbie
Posts: 1
Joined: Wed Apr 19, 2017 8:01 pm

Systemd service not configured to restart on failure

Post by unoriginalnick » Wed Apr 19, 2017 8:06 pm

I'm curious if there's a reason the systemd service files included with the EPEL 7 repo is not configured to restart the service on failure. This seems like something that would generally be desirable, especially with unreliable internet connections. I'm considering submitting a bug report or pull request, but first wanted to see if it was a deliberate decision not to do this.

User avatar
OpenVPN Protagonist
Posts: 2991
Joined: Fri Jun 03, 2016 1:17 pm

Re: Systemd service not configured to restart on failure

Post by TinCanTech » Wed Apr 19, 2017 9:24 pm

As you probably realise, OpenVPN is Free Open Source Software
and the developers are hard working, dedicated and knowledgeable volunteers.

For those developers, the integration of OpenVPN and systemd has focused on the changes
required within OpenVPN to work reliably with systemd and utilising systemd's security advantages.

Currently, due to the major release of OpenVPN 2.4 and OpenSSL 1.1, the developers have had
a considerable work load.

You are welcome to join the developer team if you have some time and skills to offer.
(You can find details on the OpenVPN wiki)

Hope that helps.

Post Reply