Description of problem: when trying to enable a service via systemctl the command fails. target service is openvpn for this discussion to be placed in the multi-user.target so service will operate at traditional runlevel 3 and 5. Version-Release number of selected component (if applicable): 3.1.1-1.fc16.x86_64 #1 SMP Fri Nov 11 21:47:56 UTC 2011 systemd-37-3.fc16.x86_64 How reproducible: configure openvpn in /etc/openvpn place client.conf, ca.crt, machinename.crt, machinename.key traditionally one would issue service openvpn start and the process pickup up the client conf file. thus issue systemctl start openvpn -- all is good. so ready to make the service come alive at boot. issue systemctl enable openvpn Failed to issue method call: No such file or directory would have expected for a link to be placed in /etc/systemd/system/multi-user.target.wants as openvpn -> /lib/systemd/system/openvpn@.service add this by hand reboot all is good.... thus the question: should this work or am I not understanding the man page for systemctl??? I am a little confused. If this is to work how does one specify the target? say just graphical(init 5) and not multi-user (init 3)? maybe this is not a bug but a feature? Have a good day!
systemctl enable does not handle instantiated units. This is bug 752774. > If this is to work how does one specify the target? say just > graphical(init 5) and not multi-user (init 3)? For this there is no support in systemctl. Manually creating the symlinks in the right directories will work though. *** This bug has been marked as a duplicate of bug 752774 ***