[Context is retrying DNS lookups when an interface appears.]
James Browning said: > When combined with some other code in the DNS path it is wrong-headed. "let's > retry DNS every 5 minutes or whenever someone acts on the netlink socket, and > pack on extra pool servers until we have twenty." It will probably come back > in a diminished form later. If you absolutely must dns_try_again periodically > it a couple of single line fixes to ntp_io:837 and ntp_io:325, switching to > true and maybe a new period respectively. Our code is full of quirks/hacks that catch obscure real-world cases. Most of the time, the code is just clutter. On the other hand, if your environment triggers that case, that small chunk of code is wonderful. I think we need a structured way of collecting and documenting this sort of thing. Should we put a big comment in the code? With a stylized tag so we can find them all. If you are working on other stuff, that's just adding to the clutter. Should we collect the descriptions in another file and add pointers both ways? -- These are my opinions. I hate spam. _______________________________________________ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
