Dear Maintainer,

= What led up to the situation? =

Chrony daemon has an option to print out all configuration settings.

This command in question is 'chronyd -p'.  The directive keyword
of Chrony configuration being impacted is 'sourcedir'.


= What exactly did you do (or not do) that was effective (or ineffective)? =

I have a file in '/run/chrony-dhcp/enp5s0.sources' that contains
somewhat relevant (to this bug report) settings.  It is only relevant
when the content of these *.sources file are NOT being printed out
by chronyd daemon using print ('-p') option.

According to 'strace -f chronyd -p', the chronyd does not make any
attempt to read *.sources files inside its 'sourcedir'
drop-in directory(s).

As a result, end-user cannot see what directive settings that
chronyd is actually 'using'.

(I've confirmed that chronyd v4.0 actually does read all files
with .sources filetype in all of its 'sourcedir' include directive(s)
as specified in its main /etc/chrony/chrony.conf' file).


= What was the outcome of this action? =

So, running:

   chronyd -p

Will not show any of the settings found in include directories
given in chrony.conf

* sourcedir /run/chrony-dhcp
* sourcedir /etc/chrony/sources.d


= What outcome did you expect instead? =

I expect to see all settings from all files found in all sourcedir
like the real chronyd daemon does.