* global.token <user authentication token>
* global.log_file <logfile full path>
- set a custom location for kamaki logging. Default values are /var/log/kamaki.log, /var/log/kamaki/clients.log /tmp/kamaki.log and ./kamaki.log
+ set a custom location for kamaki logging. Default value is ~/.kamaki.log
* global.log_token <on|off>
allow kamaki to log user tokens
$ kamaki config set log_file <logfile path>
-By default, kamaki keeps a list of possible logfile locations::
-
- /var/log/kamaki.log, /var/log/kamaki/clients.log, /tmp/kamaki.log, ./kamaki.log
+By default, kamaki logs at ~/.kamaki.log
When initialized, kamaki attempts to open one of these locations for writing, in the order presented above and uses the first accessible for appending logs. If the log_file option is set, kamaki prepends the value of this option to the logfile list, so the custom location will be the first one kamaki will attetmpt to log at.
$ kamaki livetest astakos authenticate
-The quotaholder client
-""""""""""""""""""""""
-
-A quotaholder client is introduced as an advanced feature. Quotaholder client is mostly used as a client library for accessing a synnefo quota service, but it can also be allowed as a kamaki command set, but setting the quotaholder.cli and quotaholder.url methods::
-
- [quotaholder]
- cli=quotaholder
- url=<URL of quotaholder service>
-
-Quotaholder is not tested in livetest
-
The unit testing system
"""""""""""""""""""""""