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

[Michael Biebl]

Am 17.03.2014 18:51, schrieb Alberto Gonzalez Iniesta:
> Having AUTOSTART=all *and* a openvpn option in network/interfaces does
> not look very clever. It someone uses openvpn options in their
> network/interfaces they shouldn't be using all (as in it makes no
> sense).

I see. It's just that AUTOSTART=all is the default, so this might be
configuration which is not that uncommon.


Fwiw, I noticed another issue :-)

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
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 884 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20140317/8160cd87/attachment-0002.sig>