Platform Team/Server Kit/Mace: Difference between revisions
No edit summary |
|||
| Line 12: | Line 12: | ||
== Configuration sources == | == Configuration sources == | ||
Sources for {{Code|mace}} are stored in GNU/Linux distribution agnostic manner in form | Sources for {{Code|mace}} are stored in a GNU/Linux distribution agnostic manner, in this form: | ||
[<arbitrary-path>]/<service-name>.d/[<service-confile>]/<configuration-file>.conf | [<arbitrary-path>]/<service-name>.d/[<service-confile>]/<configuration-file>.conf | ||
| Line 44: | Line 44: | ||
[''keyword''] | [''keyword''] | ||
which will tell Mace that this source file can be processed only if this particular keyword is enabled in Mace by mentioning the keyword name in the {{Code|--keywords}} command-line argument. | |||
By default, Mace has these keywords enabled: | By default, Mace has these keywords enabled: | ||
| Line 93: | Line 93: | ||
== Configuration == | == Configuration == | ||
By default, configuration | By default, configuration occurs based on several sources (sorted by applied order): | ||
* {{Code|/etc/mace.conf}} system-wide configuration file, | * {{Code|/etc/mace.conf}} system-wide configuration file, | ||
| Line 99: | Line 99: | ||
* {{Code|mace}}'s command-line arguments. | * {{Code|mace}}'s command-line arguments. | ||
Configuration files contain | Configuration files contain option names equal to command-line arguments. To get the current configuration, call: | ||
mace config | mace config | ||