Where is d.conf debian

To report a problem with the web site, e-mail debian-www lists. For other contact information, see the Debian contact page. Debian is a trademark of SPI Inc. Learn more about this site. Limit to suite: [ stretch ] [ stretch-updates ] [ stretch-backports ] [ stretch-backports-sloppy ] [ buster ] [ buster-updates ] [ buster-backports ] [ bullseye ] [ bullseye-updates ] [ bullseye-backports ] [ bookworm ] [ sid ] [ experimental ] Limit to a architecture: [ alpha ] [ amd64 ] [ arm ] [ arm64 ] [ armel ] [ armhf ] [ avr32 ] [ hppa ] [ hurd-i ] [ i ] [ ia64 ] [ kfreebsd-amd64 ] [ kfreebsd-i ] [ m68k ] [ mips ] [ mips64el ] [ mipsel ] [ powerpc ] [ powerpcspe ] [ ppc64 ] [ ppc64el ] [ riscv64 ] [ s ] [ sx ] [ sh4 ] [ sparc ] [ sparc64 ] [ x32 ].

Overview dconf is a simple key-based configuration system. Keys exist in an unstructured database but it is intended that keys that logically belong together are grouped together. Change notification is supported. Stacking of multiple configuration sources is supported.

Mandatory keys are supported. The stacking can be done at "mount points". A single configuration source may appear at multiple points in the hierarchy. This means that programs like the GDM configuration utility no longer have to be run as root. Typically, reading a key from dconf involves zero system calls and zero context switches. This is achieved with a simple file format that doubles both as the storage format for data in dconf and as an IPC mechanism between the clients and the server.

Avoiding round trips and context switches is nice in itself, but the real win comes from allowing the IO scheduler in the kernel to do a better job by saturating it with requests coming from all of the applications trying to read their keys as opposed to a common configuration server serially requesting a single key at a time.

Having all of the keys in a single compact binary format also avoids the intense fragmentation problems currently experienced by the tree-of-directories-of-xml-files approach. Writes are less optimised -- they traverse the bus and are handled by a "writer" -- a DBus service -- in the ordinary way.