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

[Alberto Gonzalez Iniesta]

On Mon, Mar 17, 2014 at 11:46:46PM +0100, Michael Biebl wrote:
> Am 17.03.2014 19:33, schrieb Alberto Gonzalez Iniesta:
> > On Mon, Mar 17, 2014 at 07:29:07PM +0100, Michael Biebl wrote:
> >> Fwiw, I noticed another issue :-)
> > 
> > #741938, fixed in -9 :-)
> > 
> >> Trying to run
> >> systemctl start openvpn at foo.conf
> >> I got
> >> Mär 17 19:22:43 pluto systemd[1]: openvpn at foo.service: control process
> >> exited, code=exited status=1
> >> Mär 17 19:22:43 pluto systemd[1]: Failed to start OpenVPN connection to foo.
> >> Mär 17 19:22:43 pluto systemd[1]: Unit openvpn at foo.service entered
> >> failed state.
> >>
> >>
> >> Apparently the /run/openvpn directory was missing.
> >>
> >> You should consider shipping a tmpfiles.d [0] snippet so this directory
> >> is properly setup (or let the daemon create that directory).
> >>
> >> [0] http://www.freedesktop.org/software/systemd/man/tmpfiles.d.html
> > 
> > Oh, I didn't know about that. I'll check that out too.
> 
> Hm, I see you moved the mkdir in /etc/init.d/openvpn around a bit.
> 
> That doesn't really help in my case, since I've disabled the SysV/LSB
> init script completely.
> 
> I don't think the native systemd .service file should have to rely on
> the SysV/LSB init script to setup the environment.

Yep, I know. The tmpfiles.d file is in place already for the next
upload. I already have something in mind to substitute the init script.
I'll send you my proposal as soon as it's ready.

Thanks,

Alberto


-- 
Alberto Gonzalez Iniesta    | Formación, consultoría y soporte técnico
mailto/sip: agi at 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