https://bugzilla.novell.com/show_bug.cgi?id=848070 https://bugzilla.novell.com/show_bug.cgi?id=848070#c2 Michal Hrusecky <mhrusecky@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|mhrusecky@suse.com | --- Comment #2 from Michal Hrusecky <mhrusecky@suse.com> 2013-11-06 08:29:26 UTC --- (In reply to comment #1)
(In reply to comment #0)
openvpn package is missing rcopenvpn script to handle start/stop.
In 12.3 I was able to use openvpn by running:
rcopenvpn start rcopenvpn stop
rcopenvpn wrapper is not present anymore in 13.1
This is not a bug. There is no init script any more, openvpn is started directly from a native template service file.
rc scripts are not tied to init scripts. We even have a nice wrapper for simple services (see rcSuSEfirewall2 or rcnscd). But I can imagine that for backward compatibility openVPN one can be little more specific - like making sure that when I run rcopenvpn start, all my configured VPNs comes to live like in 12.3.
Apart from that calling
systemctl start openvpn.target
does not start my VPNs and I have to start them manually one by one.
What does a "ls -l /etc/systemd/system/openvpn.target.wants/" say?
You have to enable the autostart of the instance(s) first:
systemctl enable [--force] openvpn@foo.service systemctl enable [--force] openvpn@bar.service
this causes to create openvpn@foo.service and openvpn@bar.service links in /etc/systemd/system/openvpn.target.wants/ pointing to the /usr/lib/systemd/system/openvpn@.service template file.
Does it solve the openvpn.target issue?
Ok, it did, so misconfiguration (or too many expectations?) on my part. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.