On Mon, Jul 06, 2015 at 12:08:37PM +0200, herrmann wrote: > Package: openvpn > Version: 2.3.4-5 > Severity: important > > Dear Maintainer, > > Problem related to systemd, Report in parts similar to 769660 - "starting a > single connection on an as-needed basis does not work with systemd" > > * What led up to the situation? > > changing the openvpn configuration > > * What exactly did you do (or not do) that was effective (or > ineffective)? > > create an additional openvpn configuration > > * What was the outcome of this action? > > new configuration didn't apply > - after openvpn start new_config > - after openvpn restart > - after openvpn stop/start > > new configuration did apply > - after shutdown -r now > > * What outcome did you expect instead? > > Even when considering the bug from 769660, at least a restart of the complete > service should start the new configuration too. It should never be neccessary > to restart the complete machine > > Workaround: Until next scheduled reboot in 20 years, Do not restart openvpn > service, but open a shadowed terminal connection to the server (or go to tty) > and start the new configuration manually, openvpn --config new_config.conf >
If you create a new openvpn configuration, you need to execute "systemctl daemon-reload" in order to the generator to create the corresponding .service file. Regards, Alberto -- Alberto Gonzalez Iniesta | Formación, consultoría y soporte técnico mailto/sip: a...@inittab.org | en GNU/Linux y software libre Encrypted mail preferred | http://inittab.com Key fingerprint = 5347 CBD8 3E30 A9EB 4D7D 4BF2 009B 3375 6B9A AA55 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
