Package: openvpn Version: 2.4.5-1 Severity: normal Dear Maintainer, when systemd is used, openvpn fails to start with an error that it cannot read its config file when /etc/openvpn/vpn.conf is a symlink to some file outside of /etc/openvpn. It seems that openvpn is chrooted before it is able to read the config file or something similar. As it works with other init systems or manually starting openvpn I suspect systemd chroots it itself instead of using --chroot.
with kind regards, Alex -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.16.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages openvpn depends on: ii debconf [debconf-2.0] 1.5.67 ii iproute2 4.17.0-2 ii libc6 2.27-3 ii liblz4-1 1.8.2-1 ii liblzo2-2 2.10-0.1 ii libpam0g 1.1.8-3.7 ii libpkcs11-helper1 1.24-1 ii libssl1.1 1.1.0h-4 ii libsystemd0 239-5 ii lsb-base 9.20170808 Versions of packages openvpn recommends: ii easy-rsa 3.0.4-1 Versions of packages openvpn suggests: ii openssl 1.1.0h-4 pn resolvconf <none> -- Configuration Files: /etc/default/openvpn changed: AUTOSTART="all" OPTARGS="" OMIT_SENDSIGS=0 -- debconf information: openvpn/create_tun: false
