Re: [systemd-devel] systemd efi boot and default entry

2016-03-30 18:49 GMT+03:00 Michal Sekletar : > > I don't believe this is currently possible. I've tried to implement > similar scheme in the past. I should probably resurrect that effort, > > https://github.com/systemd/systemd/pull/1894 > > In the meantime, you can change

Re: [systemd-devel] Different behavior when OpenVPN is started as a service through systemd

Am 31.03.2016 um 23:07 schrieb Piotr Dobrogost: When I start OpenVPN as a deamon from command line like this: `sudo OPENSSL_ENABLE_MD5_VERIFY=1 openvpn --daemon --config /etc/openvpn/xxx.conf` the tunnel comes up with no problem. However, when I start it as a systemd service I get this error:

Re: [systemd-devel] systemd efi boot and default entry

On Thu, Mar 31, 2016 at 11:10 AM, Jóhann B. Guðmundsson wrote: > > > On 03/30/2016 03:49 PM, Michal Sekletar wrote: >> >> On Mon, Mar 21, 2016 at 1:42 PM, Vasiliy Tolstov >> wrote: >> >>> Now i want to have two entries and assign priority to it via

[systemd-devel] Different behavior when OpenVPN is started as a service through systemd

Hi! When I start OpenVPN as a deamon from command line like this: `sudo OPENSSL_ENABLE_MD5_VERIFY=1 openvpn --daemon --config /etc/openvpn/xxx.conf` the tunnel comes up with no problem. However, when I start it as a systemd service I get this error: Mar 23 21:59:40 demon openvpn[10065]: VERIFY