On Sun, Mar 16, 2014 at 02:23:47AM +0100, Michael Biebl wrote: > 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).
Hi there, > 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 ] Done, changed the test. Thanks for the pointer. > - The native .systemd service file and the LSB/SysV init script name do > not match openvpn vs. openvpn@.service. > This means, during boot systemd will start the old LSB/SysV init > script. This is intentional. The functionality the old initscript provides (start a daemon for each VPN configuration file) cannot be reproduced with a .service file AFAIK. The openvpn@.service is used to replace the ability of the old init script to start a single VPN (as it allowed additional params after start/stop), also used by the openvpn option for network/interfaces declarations. > I'm afraid the current state of systemd support in openvpn is broken and > this bug should be re-opened. I disagree (after fixing #741938 in -9). 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
