On 2022-01-21 16:09:06 -0500, Scott Kitterman wrote: > On Friday, January 21, 2022 5:50:19 AM EST Vincent Lefevre wrote: > > Moreover, I don't think that reloading the system is useful in > > any case. AFAIK, the resolv.conf file is not used directly by > > postfix itself, but by the C library, which does not cache its > > contents, since it may change at any time and many running > > programs (not just daemons) use it via the C library. > > Thanks. I admit to being uncertain about which way to go for being > enabled by default. I appreciate the feedback. A restart is invasive > enough that if that's what we were talking about I would think it > should definitely not happen by default (I've run high volume > postfix instance in the past where this would have a very severe > consequence). Reload is less critical, so maybe I'm being > over-cautious to not enable it by default. I will think it over.
What I'm saying is that a reload may not even be needed. Well, I'm not sure. But for instance, if /etc/resolv.conf changes (with new DNS servers), I hope that the user doesn't have to restart his web browser, for instance. I've tried with lynx, and strace tells me that /etc/resolv.conf is reread for every new hostname resolution. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
