Configuration file suggestion about ntimed HOT 2 CLOSED

I see no problem having the configuration in a /etc/ntimed.d/ folder and read all files sequentially. Care should be taken by administrators and distributions to limit the access to that folder. Prefrably there shold be a single configuration file that supports include statements with wildcards. The standard configuration should have the different types of parameters distributed between different files like you propose. It is much easier for end users to edit a single /etc/ntimed.d/servers file then the entire /etc/ntimed.conf file.

If it is possible it would help if the syntax of the configuration file is copatible with ntpd's configuration syntax. This will help users switching over as well as making it simpler to maintain mixed environments. Unless there is any issues with the ntpd configuration format I do not see any reason to deviate from it.

from ntimed.

I have no intention of making the client program so complicated that it will require more than a single config file. In all likelyhood, I'll simply look for a /etc/ntp.conf for backwards compat reasons.

Once we get to slaves and masters things become more interesting, but we'll burn those bridges when we get to them :-)

from ntimed.