Hi guys,
On Wed, Jun 17, 2020 at 11:36:45AM +0200, Lukas Tribus wrote:
> Hello Ryan,
>
> On Mon, 15 Jun 2020 at 20:01, Ryan O'Hara wrote:
> >
> > I posted this patch to start some discussion here. I'm not the first to
> > notice
> > this problem but I was, until now, hesitant to change the syst
Hello Ryan,
On Mon, 15 Jun 2020 at 20:01, Ryan O'Hara wrote:
>
> I posted this patch to start some discussion here. I'm not the first to notice
> this problem but I was, until now, hesitant to change the systemd service
> file until now. The reason for this was that waiting for network-online.tar
I posted this patch to start some discussion here. I'm not the first to
notice this problem but I was, until now, hesitant to change the systemd
service file until now. The reason for this was that waiting for
network-online.target could delay boot time. Please see systemd network
target docs here
Change systemd service file to wait for network to be completely
online. This solves two problems:
If haproxy is configured to bind to IP address(es) that are not yet
assigned, haproxy would previously fail. The workaround is to use
"option transparent".
If haproxy us configured to use a resolver
4 matches
Mail list logo
