[Pkg-systemd-maintainers] Bug#700888: Can't start OpenVPN using ifupdown when running systemd

[Michael Biebl]

On Fri, Mar 14, 2014 at 12:29:49PM +0100, Alberto Gonzalez Iniesta wrote:
> On Fri, Mar 14, 2014 at 12:26:40PM +0100, Sylvestre Ledru wrote:
> > Hello
> > 
> > Any eta on this bug ? Since systemd will be the default for Debian
> > Jessie, it would be nice to see it fixed.
> 
> Hi Sylvestre,
> 
> The bug page is open on my browser since yesterday and I'm working on it
> now. I have to test my changes won't break sysV installs. Hope to have
> it really soon (tm).

Afaics there a few issues:
- The existence of /bin/systemctl doesn't mean that systemd is active /
  PID 1. If you want to check if systemd is running, use something like
  [ -d /run/systemd/system ]
- The native .systemd service file and the LSB/SysV init script name do
  not match openvpn vs. openvpn at .service.
  This means, during boot systemd will start the old LSB/SysV init
  script.

I'm afraid the current state of systemd support in openvpn is broken and
this bug should be re-opened.