Default page

Your IP: 216.73.216.91
Server IP: 157.245.101.34
Server: Linux skvinfotech-website 5.4.0-131-generic #147-Ubuntu SMP Fri Oct 14 17:07:22 UTC 2022 x86_64
Server Software: Apache/2.4.41 (Ubuntu)
PHP Version: 7.4.33
Buat File | Buat Folder

Dir : ~/usr/share/help/C/system-admin-guide/

Edit File: dconf-profiles.page

<credit type="author copyright">
 <name>Ryan Lortie</name>
 <email>desrt@desrt.ca</email>
 <years>2012</years>
 </credit>
 <credit type="editor">
 <name>Jana Švárová</name>
 <email>jana.svarova@gmail.com</email>
 </credit>
 <credit type="editor">
 <name>Petr Kovar</name>
 <email>pknbe@volny.cz</email>
 <years>2019</years>
 </credit>

<desc>Detailed information about profile and profile selection.</desc>
 </info>

<title>Profiles</title>

A profile is a list of configuration databases. The first
 database in a profile is the write-to database and the remaining databases
 are read-only. Each of the system databases is generated from a keyfile
 directory. Each keyfile directory contains one or more keyfiles. Each keyfile
 contains at least one dconf path and one or more keys and the corresponding
 values.

Key pairs which are set in a <sys>dconf</sys> profile will
 override the default settings unless there is a problem with the value that
 you have set.

You will usually want your <sys>dconf</sys> profile to consist of a
 user database and at least one system database. The profile must
 list one database per line.

The first line in a profile is the database that changes are written to. It
 is usually <code>user-db:<input>user</input></code>. <input>user</input> is
 the name of the user database which can normally be found in
 <file>~/.config/dconf</file>.

A <code>system-db</code> line specifies a system database. These databases
 are found in <file>/etc/dconf/db/</file>.

<example>
 <listing>
 <title>Sample profile</title>
<code its:translate="no">
user-db:user
system-db:<var>local</var>
system-db:<var>site</var>
</code>
 </listing>
 </example>

Configuring a single user and multiple system databases allows for layering
 of preferences. Settings from the <code>user</code> database file take
 precedence over the settings in the <code>local</code> database file, and the
 <code>local</code> database file in turn takes precedence over the
 <code>site</code> database file.

However, the order of precedence for <link xref="dconf-lockdown">locks</link>
 is reversed. Locks introduced in the <code>site</code> or <code>local</code>
 database files take priority over those present in <code>user</code>.

<note style="important">
 The <sys>dconf</sys> profile for a session is determined at login, so users
 will have to log out and log in to apply a new <sys>dconf</sys> user profile
 to their session.
 </note>

For more information, see the <link its:translate="no" href="man:dconf(7)">
 <cmd>dconf</cmd>(7)</link> man page.

<title>Select a profile</title>

On startup, <sys>dconf</sys> consults the <sys>DCONF_PROFILE</sys>
 environment variable. The variable can specify a relative path to a file in
 <file>/etc/dconf/profile/</file>, or an absolute path, for example, to the
 user's home directory.

If the environment variable is set, <sys>dconf</sys> attempts to open the
 named profile and aborts if that fails. If the variable is not set,
 <sys>dconf</sys> attempts to open the profile named “user”. If that
 fails, it will fall back to an internal hard-wired configuration.

For more information, see the <link its:translate="no" href="man:dconf(7)">
 <cmd>dconf</cmd>(7)</link> man page.

</section>

</page>