[systemd-devel] Different behavior when OpenVPN is started as a service through systemd

[Piotr Dobrogost]

Lennart, thanks for taking time to reply.

Lennart Poettering <lennart <at> poettering.net> writes:

> 
> This is probably something to ask the openvpn folks about.

I did this as well in this thread –
http://thread.gmane.org/gmane.network.openvpn.user/36761
 
> Note that systemd invokes services in a very minimal, cleaned-up
> execution evnironment. Maybe there's something missing for openvpn
> there, such as the right $PATH or so...

I was thinking along these lines as well. We managed to establish 
this is due openssl using secure_getenv instead of getenv (patch by 
RedHat/Fedora) and lack of appropriate SELinux policy in Fedora 24 
(Interestingly enough such policy was added in Fedora 21 but it seems it 
has since been removed).
Details at http://article.gmane.org/gmane.network.openvpn.user/36775 and
https://bugzilla.redhat.com/show_bug.cgi?id=1174915

Again, thanks for help.

Regards,
Piotr Dobrogost