Re: A new race condition in OpenVPN and Unbound services

2020-11-21 Thread Predrag Punosevac
Thanks to everyone replaying to this thread. I carefully re-reading as kindly pointed out by Stefan. I ended up implementing this paragraph Using an /etc/hostname.* file without persist-tun - OpenVPN normally re-creates the tun/tap interface at

Re: A new race condition in OpenVPN and Unbound services

2020-11-21 Thread Stuart Henderson
On 2020-11-21, Kasak wrote: > > >> 21 нояб. 2020 г., в 07:24, Predrag Punosevac >> написал(а): >> >>  >> Hi Misc, >> >> Has anybody else noticed a new race condition causing Unbound to fail >> due to the fact that OpenVPN interface is not available. >> >> Since a few releases ago I have

Re: A new race condition in OpenVPN and Unbound services

2020-11-21 Thread Kasak
> 21 нояб. 2020 г., в 07:24, Predrag Punosevac > написал(а): > >  > Hi Misc, > > Has anybody else noticed a new race condition causing Unbound to fail > due to the fact that OpenVPN interface is not available. > > Since a few releases ago I have this in my rc.conf.local to start >

Re: A new race condition in OpenVPN and Unbound services

2020-11-21 Thread Stefan Sperling
On Fri, Nov 20, 2020 at 11:21:00PM -0500, Predrag Punosevac wrote: > > Hi Misc, > > Has anybody else noticed a new race condition causing Unbound to fail > due to the fact that OpenVPN interface is not available. > > Since a few releases ago I have this in my rc.conf.local to start > openvpn

A new race condition in OpenVPN and Unbound services

2020-11-20 Thread Predrag Punosevac
Hi Misc, Has anybody else noticed a new race condition causing Unbound to fail due to the fact that OpenVPN interface is not available. Since a few releases ago I have this in my rc.conf.local to start openvpn server and unbound openvpn_flags=--config /etc/openvpn/server.conf