<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>linux on TedNote</title>
    <link>https://tednote.com/tags/linux/</link>
    <description>Recent content in linux on TedNote</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <managingEditor>thardenb&#43;pages@gmail.com (Ted Hardenburgh)</managingEditor>
    <webMaster>thardenb&#43;pages@gmail.com (Ted Hardenburgh)</webMaster>
    <lastBuildDate>Fri, 12 Jun 2020 08:30:26 -0700</lastBuildDate><atom:link href="https://tednote.com/tags/linux/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Configuring HAProxy Service on CentOS</title>
      <link>https://tednote.com/post/2020-06-12-haproxy-centos-service/</link>
      <pubDate>Fri, 12 Jun 2020 08:30:26 -0700</pubDate>
      <author>thardenb&#43;pages@gmail.com (Ted Hardenburgh)</author>
      <guid>https://tednote.com/post/2020-06-12-haproxy-centos-service/</guid>
      <description>I&amp;rsquo;ve worked with a customer to get a HAProxy load balancer setup on CentOS 8.0 and ran into an issue with the service that was created. If the Linux VM was restarted, HAProxy would fail to start and it appeared to be related to the network not being available.
Looking around the interwebs, I found the option that was added by default was the culprit. In the haproxy.service file there is a [Unit] section that assigns when the service should start up and it was set to:</description>
    </item>
    
  </channel>
</rss>
