<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""></div></div><div><blockquote type="cite" class=""><div class="">On Dec 19, 2018, at 10:45 AM, James Abernathy <<a href="mailto:jfabernathy@gmail.com" class="">jfabernathy@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><blockquote type="cite" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><blockquote type="cite" class=""><br class="Apple-interchange-newline">I think for safety sake, I'd use the full-internet.service and<br class="">wait-until-pingable.py approach. But since wait-until-pingable.py waits<br class="">for what it wants, the "After=NetworkManager-wait-online.service" could<br class="">really be anything network related because the script waits, right??<br class=""><br class="">-------------------------------------full-internet.service------------------------<br class=""><br class="">[Unit]<br class="">Description=Wait for full internet service to be available including DNS<br class="">After=NetworkManager-wait-online.service<br class=""><br class="">[Service]<br class="">Type=simple<br class="">ExecStartPre=/usr/local/bin/wait-until-pingable.py <a href="http://my.hdhomerun.com" class="">my.hdhomerun.com</a> 30<br class="">ExecStart=/bin/true<br class=""><br class="">[Install]<br class="">WantedBy=multi-user.target<br class=""></blockquote>Yes, if you do not want to have NetworkManager-wait-online.service<br class="">enabled, or are not using NetworkManager, you could just have<br class="">full-internet.service run After=network.target. That way, with the<br class="">next update of wait-until-pingable.py, you would also get a log<br class="">message that tells you how long it had to wait for the network to<br class="">complete coming up.<br class=""></blockquote><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">Since my production system only uses Ubuntu Server and static IPs, there is no need for NetworkManager. So after network.target would be an improvement. I'll test all this some more.</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">Jim A</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><br class=""></div></blockquote><div><br class=""></div>So the first test is to start over and see what’s installed by default. I installed Ubuntu Server 18.04.1 with no snaps or packages. I took the defaults on everything. Since my eno1 mac address is in my router as fixed to an IP, I went with the default DHCP and got the right address from my router.</div><div><br class=""></div><div>1) NetworkManager is not installed </div><div>2) systemd-networkd-wait-onine.service is enabled and active</div><div>3) network.target is enabled and active</div><div><br class=""></div><div>I’ll install mythtv-backend with mythhdhrrecorder and see what we get with the different delaying tactics for mythtv-backend.service</div><div><br class=""></div><div>Jim A</div><div><br class=""></div><div><br class=""></div><div><br class=""></div><div><br class=""></div><br class=""></body></html>