GSETTINGS(1) User Commands GSETTINGS(1)NAME
gsettings - GSettings configuration tool
SYNOPSIS
gsettings get SCHEMA [:PATH] KEY
gsettings monitor SCHEMA [:PATH] [KEY]
gsettings writable SCHEMA [:PATH] KEY
gsettings range SCHEMA [:PATH] KEY
gsettings set SCHEMA [:PATH] KEY VALUE
gsettings reset SCHEMA [:PATH] KEY
gsettings reset-recursively SCHEMA [:PATH]
gsettings list-schemas
gsettings list-relocatable-schemas
gsettings list-keys SCHEMA [:PATH]
gsettings list-children SCHEMA [:PATH]
gsettings list-recursively [SCHEMA [:PATH]]
gsettings help [COMMAND]
DESCRIPTION
gsettings offers a simple commandline interface to GSettings. It lets you get, set or monitor an individual key for changes.
The SCHEMA and KEY arguments are required for most commands to specify the schema id and the name of the key to operate on. The schema id
may optionally have a :PATH suffix. Specifying the path is only needed if the schema does not have a fixed path.
When setting a key, you also need specify a VALUE The format for the value is that of a serialized GVariant, so e.g. a string must include
explicit quotes: "'foo'". This format is also used when printing out values.
COMMANDS
get
Gets the value of KEY. The value is printed out as a serialised GVariant.
monitor
Monitors KEY for changes and prints the changed values. If no KEY is specified, all keys in the schema are monitored. Monitoring will
continue until the process is terminated.
writable
Finds out whether KEY is writable.
range
Queries the range of valid values for KEY.
set
Sets the value of KEY to VALUE. The value is specified as a serialised GVariant.
reset
Resets KEY to its default value.
reset-recursively
Reset all keys under the given SCHEMA.
list-schemas
Lists the installed, non-relocatable schemas. See list-relocatable-schemas if you are interested in relocatable schemas.
list-relocatable-schemas
Lists the installed, relocatable schemas. See list-schemas if you are interested in non-relocatable schemas.
list-keys
Lists the keys in SCHEMA.
list-children
Lists the children of SCHEMA.
list-recursively
Lists keys and values, recursively. If no SCHEMA is given, list keys in all schemas.
help
Prints help and exits.
GIO GSETTINGS(1)
Check Out this Related Man Page
UNI(8) System Manager's Manual UNI(8)NAME
uni - a program to interface with the UniConf configuration system
SYNOPSIS
uni get KEY [DEFAULT]
uni set KEY [VALUE]
uni xset KEY [VALUE]
uni keys KEY
uni hkeys KEY
uni xkeys KEY
uni dump KEY
uni hdump KEY
uni xdump KEY
DESCRIPTION
UniConf is the One True Configuration system that includes all the others because it has plugin backends and frontends. Or, less
grandiosely, it's a lightweight, distributed, cacheable tree of strings.
uni is used to interface directly with the UniConf system. It's primary use is for diagnostic purposes, but it can be used to add UniConf
support to shell scripts.
ENVIRONMENT VARIABLE
UNICONF
Before using uni, you must tell it which UniConf moinker you wish to query by setting this environment variable.
Monikers are used to contact UniConf back-ends, be they a uniconfd server, or a local file. For example, they could be:
o a filename (ini:/var/lib/app/config.ini),
o or a network address, (tcp:open.nit.ca:4111).
COMMANDS
get Retreive the VALUE associated with the provided KEY within the UniConf database. If a DEFAULT is provided, this will be returned if
the KEY has no associated VALUE.
set Assign the provided VALUE the the provided KEY. UniConf provides no guarentee that the entry committed throughout the database.
The next "get" command for this KEY may not return the most recently "set" value due to caching, or the existance of a read-only
generator.
xset Assign, to the provided KEY, the contents of the standard-input stream. Use this command to pipe information into the UniConf data-
base.
keys List all the sub-keys contained within the provided KEY.
hkeys List all the sub-keys, recursively, contained within the provided KEY. Since any KEY may contain sub-keys, UniConf provides no
guarentee that there are no circular references.
xkeys List all the sub-keys contained within the provided KEY, which can contain wildcards. See the WILDCARDS section.
dump List all the sub-keys and their values, contained within the provided KEY.
hdump List all the sub-keys and their values, recursively, contained within the provided KEY.
xdump List all the sub-keys and their values, contained within the provided KEY, which can contain wildcards.
WILDCARDS
A KEY looks just like a normal slash-delimited path. The root of the UniConf tree has a KEY named "/". Sub-keys can be accessed by names
such as "/software/myapp/version".
With wildcards, you can access more than one key at a time.
* To access a sub-key within any one level of keys, use the asterix like so: "/software/*/version". This retrieves all keys of "ver-
sion" that are one level beneath "/software".
... To access a sub-key anywhere beneath a key, use the ellipsis like so: "/.../version". This retrieves all keys of "version" that are
zero or more levels beneath the root (i.e. any appearance of "version" within the database.
SEE ALSO uniconfd(8)AUTHORS
This software was written by the hackers at Net Integration Technologies. Contact us at <wvstreams-dev@lists.nit.ca>
Uni 4.4.1 September 2004 UNI(8)