Sections
- [<servername> <client>]
- [<servername> LIMIT]
+ [<servername> - <client>]
[<client>]
[<servername>] often [SERVER]
- [LIMIT]
[COMMON]
- [DEFAULT]
Keys are looked up in that order, unless otherwise specified.
<client> is the client's virtual address.
-<servername> must be a valid lowercase DNS hostname and not look like
-an address, or be COMMON, DEFAULT or SERVER.
-
-Things not in a section are an error.
-
-
-Both client and server read the files
- /etc/hippotat/main.cfg
- /etc/hippotat/config.d/*
- /etc/hippotat/secrets.d/*
-and in each case if it's a directory, all contained files whose
-names consists of only ascii alphanumerics plus '-' and '_'.
-
-The ini file format sections from these files are all unioned.
-Later files (in the list above, or alphabetically later) can
-override settings from earlier ones.
-
-Note that although it is conventional for information for a particular
-server or client to be in a file named after that endpoint, there is
-no semantic link: all the files are always read and the appropriate
-section from each is applied to every endpoint.
-
-(If main.cfg does not exist, master.cfg will be tried for backward
-compatibility reasons.)
-
+<servername> must be a valid DNS hostname and not look like an address.
Exceptional settings: