<div dir="ltr"><div dir="ltr">On Fri, Feb 5, 2021, at 3:20 PM Hal Murray via devel <<a href="mailto:devel@ntpsec.org" target="_blank">devel@ntpsec.org</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
[Context is retrying DNS lookups when an interface appears.]<br>
<br>
James Browning said:<br>
> When combined with some other code in the DNS path it is wrong-headed. "let's<br>
> retry DNS every 5 minutes or whenever someone acts on the netlink socket, and<br>
> pack on extra pool servers until we have twenty." It will probably come back<br>
> in a diminished form later. If you absolutely must dns_try_again periodically<br>
> it a couple of single line fixes to ntp_io:837 and ntp_io:325, switching to<br>
> true and maybe a new period respectively. <br>
<br>
Our code is full of quirks/hacks that catch obscure real-world cases. Most of <br>
the time, the code is just clutter. On the other hand, if your environment <br>
triggers that case, that small chunk of code is wonderful.<br>
<br>
I think we need a structured way of collecting and documenting this sort of <br>
thing.<br>
<br>
Should we put a big comment in the code? With a stylized tag so we can find <br>
them all. If you are working on other stuff, that's just adding to the <br>
clutter.<br></blockquote><div><br></div><div>I read on the Internet that comments are useless. I occasionally notice them despite the fade to gray tendency. Yeah, I ripped out the following. It was essentially invisible in my not-an-ide and the rat brain is fallible.</div>- /*<br>- ** Classic Bug 2672: Some OSes (MacOSX, Linux) don't block spoofed ::1<br><div>- */</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Should we collect the descriptions in another file and add pointers both ways?<br></blockquote><div><br></div><div>Possibly. If it happens I would like to start the name suggestions with 'codescars' after [1] and something I thought I had read on an Internet site but can no longer find there.</div><div><br></div><div>[1] <a href="http://www.labelscar.com/" target="_blank">http://www.labelscar.com/</a></div></div></div>