Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

uniconfd(8) [suse man page]

UNICONFD(8)						      System Manager's Manual						       UNICONFD(8)

NAME
uniconfd - a daemon program for the UniConf configuration system SYNOPSIS
uniconfd [ OPTIONS ] MOUNT ... 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. It supports: o retrieving, storing, and enumerating key/value pairs (where both keys and values are strings). o multiple backends where the actual key/value pairs are stored. o multiple frontends for tying it to other configuration architectures. It operates locally, and across a network, allowing you to tie multiple different applications together for distributed computing. Also, it provides notifications in the form of callbacks, so your application can be notified if a configuration key has changed. uniconfd is necessary when you have more than one application, or multiple instances of an application, sharing one configuration. Uni- Conf-enabled applications contact uniconfd which provides notifications when any of their watched keys change. You tell uniconfd which UniConf MOUNT you want it to manage. See the MOUNTS section for more information. OPTIONS
-f Run in the foreground. Do not fork into a separate daemon process. -d, -dd Print debugging messages to the console. The second d increases the verbosity of the messages. -V Print the version number and exit. -a Require authentication on incoming connections. -A Check all accesses against a perms moniker. -p port Listen on a given TCP port. The default is 4111. If port is 0, then listening on TCP is disabled. -s port Listen on a given TCP port wrapped in SSL. The default is 4112. If port is 0, then listening on SSL-over-TCP is disabled. -u filename Listen on a given Unix socket filename. This is disabled by default. MOUNTS
Mounts are UniConf path monikers which are in the form: /SUBTREE=GENERATORS:PATH SUBTREE This is the tree to manage. All trees are descended from the root tree, indicated by a bare slash (/). GENERATORS These are the generators used to read and write key/value pairs. You can chain them with colons. For example, the generator chain: cache:retry:ini will cache the configuration for speed, retry persistently if the data source disappears, and store the data in an INI-formatted file. PATH This is the location where the data is stored. It is dependent on which GENERATORS were specified. For instance, it could be: o a filename (ini:/var/lib/app/config.ini), o a network address, (tcp:open.nit.ca:4111), o or even an empty string (tmp:). Examples: /=tmp: /ca/nit=ssl:open.nit.ca /ca/nit/uniconfd=ini:/var/lib/uniconfd/uniconfd.ini /apps=cache:retry:unix:/var/lib/apps/socket FILES
/etc/uniconfd.conf /var/lib/uniconf/uniconfd.ini /var/lib/uniconf/uniconf.ini AUTHORS
This software was written by the hackers at Net Integration Technologies. Contact us at <wvstreams-dev@lists.nit.ca> UniConfDaemon 4.4.1 August 2004 UNICONFD(8)

Check Out this Related Man Page

odbcinst.ini(5) 					       unixODBC manual pages						   odbcinst.ini(5)

NAME
/etc/odbcinst.ini - An unixODBC drivers configuration DESCRIPTION
/etc/odbcinst.ini is a text configuration file for unixODBC drivers. It can be edited by hand, but the recommended way to update this file is to use the odbcinst(1) utility. FILE FORMAT
The general .ini file format is: [SectionName1] key1 = value1 key2 = value2 ... [SectionName2] key1 = value1 key2 = value2 ... Each ODBC driver has its own section and can be referred to by the name of its section. Recognized configuration keys are: Description A text string briefly describing the driver. Driver A filesystem path to the actual driver library. Setup A filesystem path to the driver setup library. FileUsage odbcinst(1) entry, if you edit the configuration file by hand, you have to supply it yourself. TEMPLATE FILES The recommended way to manage the drivers is using the odbcinst(1) utility. You can install the drivers by supplying it with template file, which has the same format as this file. EXAMPLES
An example of the actual PostgreSQL driver: [PostgreSQL] Description = PostgreSQL driver for GNU/Linux Driver = /usr/lib/psqlodbcw.so Setup = /usr/lib/libodbcpsqlS.so FileUsage = 1 By specifying the driver like that, you can then reference it in the odbc.ini(5) as follows: Driver = PostgreSQL The recommended way to add that driver is by creating template file containg: [PostgreSQL] Description = PostgreSQL driver for GNU/Linux Driver = /usr/lib/psqlodbcw.so Setup = /usr/lib/libodbcpsqlS.so and call the odbcinst(1): # odbcinst -i -d -f template.ini SEE ALSO
odbcinst(1), odbc.ini(5) AUTHORS
The authors of unixODBC are Peter Harvey <pharvey@codebydesign.com> and Nick Gorham <nick@easysoft.com>. For the full list of contributors see the AUTHORS file. COPYRIGHT
unixODBC is licensed under the GNU Lesser General Public License. For details about the license, see the COPYING file. version 2.3.1 Thu 27 Jun 2013 odbcinst.ini(5)
Man Page