Everything that uses configuration files should report where they're located
Programs should not only report where the configuration files are located, but also report how configuration <i>options</i> contained therein are read in:<p>Some programs use a &quot;<i>last</i> occurrence wins&quot; approach, while other programs (e.g. sshd) use a &quot;<i>first</i> occurrence wins&quot; approach.<p>Buried in <a href="https:&#x2F;&#x2F;man.freebsd.org&#x2F;cgi&#x2F;man.cgi?sshd_config(5)" rel="nofollow noreferrer">https:&#x2F;&#x2F;man.freebsd.org&#x2F;cgi&#x2F;man.cgi?sshd_config(5)</a> and awkwardly expressed:<p>&quot;Unless noted otherwise, for each keyword, the first obtained value will be used.&quot;<p>That&#x27;s why e.g. Debian&#x27;s <i>&#x2F;etc&#x2F;ssh&#x2F;sshd_config</i> (  <a href="https:&#x2F;&#x2F;salsa.debian.org&#x2F;ssh-team&#x2F;openssh&#x2F;-&#x2F;blob&#x2F;debian&#x2F;1%9.3p1-1&#x2F;sshd_config?ref_type=tags#L13" rel="nofollow noreferrer">https:&#x2F;&#x2F;salsa.debian.org&#x2F;ssh-team&#x2F;openssh&#x2F;-&#x2F;blob&#x2F;debian&#x2F;1%...</a> ) starts with<p><pre><code>  Include &#x2F;etc&#x2F;ssh&#x2F;sshd_config.d&#x2F;*.conf
</code></pre>
, so that custom configurations in that directory win over the distribution-provided defaults set up after this Include directive inside <i>&#x2F;etc&#x2F;ssh&#x2F;sshd_config</i>.