cfget(1) [debian man page]
CFGET(1) User Commands CFGET(1) NAME
cfget - get values from a config file SYNOPSIS
cfget [options] section/key cfget [options] --dump=STYLE [section/key [section/key...]] cfget [options] --template=STYLE [infile [outfile]] DESCRIPTION
Get values from a config file. cfget is a simple tool to read values from configuration files. It is useful, for example, to create configurable shellscripts or make- files. It can also be configured to support virtual configuration values that, if not present in the config file, are automatically computed from the existing values. This makes it convenient, for example, to get a "duration" value from a configuration file that only contains a "start date" and an "end date". OPTIONS
--version show program's version number and exit -h, --help show this help message and exit -q, --quiet quiet mode: only output fatal errors -v, --verbose verbose mode --debug verbose mode -C file, --cfg=file config file to read; the option can be given more than once to read more than one file. If missing, read a colon separated list from the CFGET_CFG env variable. -P file, --plugin=file list of plugin files or directories to load. The option can be given more than once to read more than one file. If missing, read a colon separated list from the CFGET_PLUGINS env variable. -d name, --dump=name dump the contents of the database using the given style. Use '--dump=list' for a list of available styles. If one or more paths are provided in the command line, dump only those paths, otherwise dump all. -t name, --template=name read a template file, expand template placeholders using the configuration data and output the result. Use '--template=list' for a list of available styles. -f name, --format=name use a custom configuration file format (default: ini). Use '--format=list' for a list of available formats. The CFGET_FORMAT envi- ronment value, if defined, can be used to provide a different default value. -r path, --root=path restrict all work to values under the given path EXAMPLES
# Get a key from a config file cfget -C file.ini general/name # More can be specified, they will be searched in order cfget -C general.ini -C local.ini general/name # Use a plugin to add virtual entries cfget -C file.ini --plugin=virtual.py general/name # A plugin can also a directory containing .py files # and plugins can also be specified more than once cfget -C file.ini --plugin=virtual.py --plugin=virtual/ general/name # In a shellscript, you may want to use environment variables if you # invoke cfget many times: #!/bin/sh CFGET_CFG=general.ini:local.ini CFGET_PLUGINS=virtual.py:virtual/ START=`cfget general/start` END=`cfget general/end` DURATION=`cfget general/duration` # Quick way to copy all config values to the environment eval `cfget --dump=exports -C file.ini` # Autoconf-style template substitution cfget --template=autoconf -C file.ini script.in script # Curly braces substitude literally cfget -C file.ini "general/start_{general/type}" # One can use simple expressions cfget -C file.ini "general/start + general/duration" cfget -C file.ini "round(general/age / 2)" AUTHOR
cfget has been written by Enrico Zini <enrico@enricozini.org>. cfget 0.15 July 2010 CFGET(1)
Check Out this Related Man Page
SCRIPTMGR(1) SCRIPTMGR(1) NAME
scriptmgr - utility for controlling other skytools scripts. SYNOPSIS
scriptmgr.py [switches] config.ini <command> [-a | job_name ... ] DESCRIPTION
scriptmgr is used to manage several scripts together. It discovers potential jobs based on config file glob expression. From config file it gets both job_name and service type (that is the main section name eg [cube_dispatcher]). For each service type there is subsection in the config how to handle it. Unknown services are ignored. COMMANDS
status scriptmgr config.ini status Show status for all known jobs. start scriptmgr config.ini start -a scriptmgr config.ini start job_name1 job_name2 ... launch script(s) that are not running. stop scriptmgr config.ini stop -a scriptmgr config.ini stop job_name1 job_name2 ... stop script(s) that are running. restart scriptmgr config.ini restart -a scriptmgr config.ini restart job_name1 job_name2 ... restart scripts. reload scriptmgr config.ini reload -a scriptmgr config.ini reload job_name1 job_name2 ... Send SIGHUP to scripts that are running. CONFIG
Common configuration parameters job_name Name for particulat job the script does. Script will log under this name to logdb/logserver. The name is also used as default for PgQ consumer name. It should be unique. pidfile Location for pid file. If not given, script is disallowed to daemonize. logfile Location for log file. loop_delay If continuisly running process, how long to sleep after each work loop, in seconds. Default: 1. connection_lifetime Close and reconnect older database connections. log_count Number of log files to keep. Default: 3 log_size Max size for one log file. File is rotated if max size is reached. Default: 10485760 (10M) use_skylog If set, search for [./skylog.ini, ~/.skylog.ini, /etc/skylog.ini]. If found then the file is used as config file for Pythons logging module. It allows setting up fully customizable logging setup. scriptmgr parameters config_list List of glob patters for finding config files. Example: config_list = ~/dbscripts/conf/*.ini, ~/random/conf/*.ini Service section parameters cwd Working directory for script. args Arguments to give to script, in addition to -d. script Path to script. Unless script is in PATH, full path should be given. disabled If this service should be ignored. Example config file [scriptmgr] job_name = scriptmgr_livesrv logfile = ~/log/%(job_name)s.log pidfile = ~/pid/%(job_name)s.pid config_list = ~/scripts/conf/*.ini # defaults for all service sections [DEFAULT] cwd = ~/scripts [table_dispatcher] script = table_dispatcher.py args = -v [cube_dispatcher] script = python2.4 cube_dispatcher.py disabled = 1 [pgqadm] script = ~/scripts/pgqadm.py args = ticker COMMAND LINE SWITCHES
Following switches are common to all skytools.DBScript-based Python programs. -h, --help show help message and exit -q, --quiet make program silent -v, --verbose make program more verbose -d, --daemon make program go background Following switches are used to control already running process. The pidfile is read from config then signal is sent to process id specified there. -r, --reload reload config (send SIGHUP) -s, --stop stop program safely (send SIGINT) -k, --kill kill program immidiately (send SIGTERM) Options specific to scriptmgr: -a, --all Operate on all non-disabled scripts. 03/13/2012 SCRIPTMGR(1)