Changes

Jump to navigation Jump to search
m
Line 10: Line 10:  
* mace doesn't function like a daemon; it just converts configuration sources to the final configuration on the final server, e.g., as a post procedure after installing packages;
 
* mace doesn't function like a daemon; it just converts configuration sources to the final configuration on the final server, e.g., as a post procedure after installing packages;
 
* mace is designed to ease support of intermediate customizing, i.e., the original configuration, provided by an upstream project, might be supplemented (not patched) in the downstream product before deploying it to the final users.
 
* mace is designed to ease support of intermediate customizing, i.e., the original configuration, provided by an upstream project, might be supplemented (not patched) in the downstream product before deploying it to the final users.
* within the [[Sugar Server Kit]] initiative, mace is intended to support mostly only [[Sugar_Server_Kit/Architecture#Dumb_school_servers|Dumb school servers]] functional model.
+
* within the [[Sugar Server Kit]] initiative, mace is intended to support, mostly, only the [[Sugar_Server_Kit/Architecture#Dumb_school_servers|Dumb school servers]] functional model.
    
== Configuration sources ==
 
== Configuration sources ==
Line 113: Line 113:     
  mace config
 
  mace config
 +
 +
== Troubleshooting ==
 +
 +
* By default, if mace can't start configuring services with new configuration, it falls back to the old configuration. It might be not very useful in case of investigating new configuration errors. To prevent such behavior use {{Code|-R}} command-line argument and try to start affected service manually (with new configuration):
 +
 +
mace apply -R
 +
/etc/init.d/<SERVICE> start
    
== Testing routines ==
 
== Testing routines ==

Navigation menu