I would like to get this figured out as well. After spending the last week building a bunch of FC 16 servers, I am starting to see how it hangs together and concur. An interesting comment in the bug listed above was about the lack of documentation on systemctl. In the case of openvpn the lack of a distro README doesn't help.ĭownside is that not all the services have been integrated and standardised. The catch seems to be that if you are passing information in the service name, after an there is no defined standard. I do quite like the way that systemctl reduces the steps for administration to enable a service to three steps. Training people on the new systemctl as the "correct" way of controlling your services "should" make life easier. As all the service are migrating to use the systemctl, I decided to integrate it how the system "should" work for standardisation.
Having found a posted solution for tigervnc-server, I next looked at my openvpn problem.
The normal process for enabling a package:ĭoesn't work out of the box for openvpn and also for tigervnc-server (and probably an number of others I haven't found). The base yum install on FC 16 did not completely integrate the package into systemctl. What I was trying to do was integrate it into the systemctl the way all the other packages have mostly been done for consistency. True I could have done that and it would have been a quick and simple solution. Then checked it was still ~]# systemctl status - OpenVPN Robust And Highly Flexible Tunneling Application On serverĪctive: active (running) since Mon, 21:34:41 +1000 2min 16s agoĬGroup: 14553 /usr/sbin/openvpn -daemon -writepid /var/run/openvpn/server.pid -cd /etc/openvpn/ -config nf It worked after I ran the service for the first time. I found the command that nirik had posted above in the thread and tried it with no success. My assumption is that when I ran the service for the first time it created it. In my directory searches before, that file was not there. # ln -s I re-enabled selinux and it broke. Once the service was running I could then add a link. #systemctl start important thing is that the name of the openvpn config file you wish to use is the one placed after the In my case my server config file is named "nf"
Having worked through this issue on my vpn server the solution I found was in a Bugzilla report:
0 kommentar(er)
