Am 27.08.2012 00:20, schrieb jdow:
On 2012/08/25 15:07, Reindl Harald wrote:
Am 26.08.2012 00:00, schrieb Timothy Murphy:
Marko Vojinovic wrote:
In what sense openvpn *doesn't* run like every other service?
Before systemd/systemctl came along I just used to say "chkconfig openvpn on". I'm just asking why I can't do the equivalent today?
As far as I know, one can "systemctl enable" every other service.
how often do we start this discussion how did yu enable DIFFERENT openvpn-connections before systemd? why do you no simply create ION file to do what you like?
/etc/systemd/system/openvpn.service:
[Unit] Description=OpenVPN After=syslog.target network.target network-wlan-bridge.service
[Service] Type=forking ExecStart=/usr/sbin/openvpn --daemon --cd /etc/openvpn/ --config openvpn.conf Restart=always RestartSec=1
[Install] WantedBy=multi-user.target
So I suppose that magical incantation is so much more obvious that chkconfig, which just worked, had to be done away with. Riiiiight! If it's not broke let's fix it anyway.
boah you can even type "chkconfig openvpn on" if the unit-file like above exists - systemd is great, only the way it was introduced in Fedora with most packages not prepared which is still the case for a lot of is really poor
normally it owuld be the job of a DISTRIBUTIOn to take care of such conversions instead release half baken bread
BUT this doe snot change the fact that a unitfile like above is written within 20 seconds, look at the sysvinit script for openvpn - was this really easier to understand?