Re: [gentoo-user] Re: systemd + openvpn
On Thu, Feb 12, 2015 at 11:37 PM, Joseph syscon...@gmail.com wrote: No, the problem in Fedora was thier selinux. I suppose to be some extra security, but it seems to me it creates only more problems. A common observation with SELinux. Even so, it definitely DOES provide additional security. It is a standard Linux feature and available on Gentoo as well. If the configuration isn't right (and it is easy to get it wrong) then you'll have problems. I forget all the details of SELinux, but you should be able to put it in a mode that logs but does not enforce. Using those logs you should be able to determine exactly what roles/permissions/labels/etc are missing. I suspect that if you just dumped the relevant logs on Fedora's bugzilla that they'd fix their openvpn package for you. If I had a working SELinux setup I wouldn't be too quick to just completely disable it over one package. -- Rich
Re: [gentoo-user] Re: systemd + openvpn
On 02/11/15 19:26, Rich Freeman wrote: On Wed, Feb 11, 2015 at 6:26 PM, walt w41...@gmail.com wrote: Yes, I see the same, which I feel is a systemd bug. The escaping trick works only with the 'enable' command, not stop or start. Dumb. It seems more likely to be an error with the unit, which has nothing to do with systemd. As I mentioned already, I had to make some changes in mine. If you write a bad init.d scripts, that isn't an openrc bug either. :) -- Rich No, the problem in Fedora was thier selinux. I suppose to be some extra security, but it seems to me it creates only more problems. So I disabled it, and openvpn connects just fine. I was able to install on it nxclient-3.5 as well, it works fine. -- Joseph
Re: [gentoo-user] Re: systemd + openvpn
On 02/11/15 15:26, walt wrote: On 02/11/2015 02:38 PM, Joseph wrote: On 02/11/15 13:52, walt wrote: On 02/11/2015 10:58 AM, Joseph wrote: on Fedora when I do systemctl enable openvpn@eeepc.service I get: Failed to execute operation: No such file or directory. You need to escape the @ by typing openvpn\@eeepc.service, which is not clear from the error message. I'm still getting the same failed error message. systemctl start openvpn\@eeepc.service Yes, I see the same, which I feel is a systemd bug. The escaping trick works only with the 'enable' command, not stop or start. Dumb. As an experiment you might try systemctl start openvpn\* or even openvpn[@]eeepc in case regexps might work. BTW the .service is optional, systemd assumes it as the default. Thanks for trying to help. I'm getting the same error message :-/ Trying to install Gentoo on it will take me 1-2 weeks :-/ so I was looking for an alternative. -- Joseph
Re: [gentoo-user] Re: systemd + openvpn
On 02/11/15 13:52, walt wrote: On 02/11/2015 10:58 AM, Joseph wrote: on Fedora when I do systemctl enable openvpn@eeepc.service I get: Failed to execute operation: No such file or directory. You need to escape the @ by typing openvpn\@eeepc.service, which is not clear from the error message. I'm still getting the same failed error message. systemctl start openvpn\@eeepc.service -- Joseph
Re: [gentoo-user] Re: systemd + openvpn
On Wed, Feb 11, 2015 at 6:26 PM, walt w41...@gmail.com wrote: Yes, I see the same, which I feel is a systemd bug. The escaping trick works only with the 'enable' command, not stop or start. Dumb. It seems more likely to be an error with the unit, which has nothing to do with systemd. As I mentioned already, I had to make some changes in mine. If you write a bad init.d scripts, that isn't an openrc bug either. :) -- Rich
