UNICONFD(8)

πŸ’– UNICONFD πŸ’–

okay bestie, gather round, because this is uniconfd from section 8 of the System Manager's Manual, and she is the daemon program for the UniConf configuration system. yes. THE. πŸŽ€


✨ NAME ✨

uniconfd β€” a daemon program for the UniConf configuration system. that's it, that's the girl. πŸ’…


🌸 SYNOPSIS 🌸

uniconfd [ OPTIONS ] MOUNT ...

so you give her some OPTIONS, you give her one or more MOUNTs, and she goes to work. periodt. ✨


πŸ¦‹ DESCRIPTION πŸ¦‹

UniConf is the One True Configuration system, no cap β€” it includes all the others because it has plugin backends and frontends. or, if we're being less grandiosely about it, it's a lightweight, distributed, cacheable tree of strings. 🌈

It supports:

  • retrieving, storing, and enumerating key/value pairs (where both keys and values are strings). yes both. strings. πŸ’œ
  • multiple backends where the actual key/value pairs are stored.
  • 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. and β€” this is the part β€” 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. UniConf-enabled applications contact uniconfd, which provides notifications when any of their watched keys change. it's giving group chat moderator energy fr fr. 🫢

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. she stays right here with you. πŸ₯Ί
  • -d, -dd β€” print debugging messages to the console. the second d increases the verbosity of the messages. one d is a lil chatty, two ds is unhinged chatty. πŸ’€
  • -V β€” print the version number and exit. short and sweet.
  • -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 (/). yes, just a lonely little slash. iconic.

πŸ’œ 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. stack them like bracelets bestie. ✨

πŸŽ€ PATH

this is the location where the data is stored. it is dependent on which GENERATORS were specified. for instance, it could be:

  • a filename (ini:/var/lib/app/config.ini),
  • a network address, (tcp:open.nit.ca:4111),
  • 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> πŸ’Œ


and that's the whole vibe bestie!! this is UniConfDaemon version 4.6.1, dated August 2004 β€” yeah she's vintage, she's a classic, and she's still serving. mwah. πŸ’–βœ¨πŸ¦‹

πŸ“¦ where this page comes from