[gnome-user-docs] Content added from live pages
- From: Michael Hill <mdhill src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [gnome-user-docs] Content added from live pages
- Date: Mon, 2 Jul 2012 17:13:11 +0000 (UTC)
commit df71561cddef866f9aa05222ab41bd462eab5d2e
Author: Michael Hill <mdhillca gmail com>
Date: Mon Jul 2 13:09:08 2012 -0400
Content added from live pages
system-admin-guide/C/dconf-profiles-edit.page | 22 +++++++++++++
system-admin-guide/C/dconf-profiles.page | 42 ++++++++++++++++--------
system-admin-guide/C/gsettings-browse.page | 32 +++++++++++++++++++
system-admin-guide/C/index.page | 8 +++++
system-admin-guide/C/lockdown.page | 38 ++++++++++++++--------
system-admin-guide/C/processes.page | 29 +++++++++++++++++
6 files changed, 143 insertions(+), 28 deletions(-)
---
diff --git a/system-admin-guide/C/dconf-profiles-edit.page b/system-admin-guide/C/dconf-profiles-edit.page
new file mode 100644
index 0000000..d4c865a
--- /dev/null
+++ b/system-admin-guide/C/dconf-profiles-edit.page
@@ -0,0 +1,22 @@
+<page xmlns="http://projectmallard.org/1.0/"
+ type="topic" style="task"
+ id="dconf-profiles-edit">
+ <info>
+ <revision version="0.1" date="2012-07-02" status="stub"/>
+ <link type="guide" xref="index" group="tools" />
+
+ <credit type="author copyright">
+ <name>Matthias Clasen</name>
+ <email>matthias clasen gmail com</email>
+ <years>2012</years>
+ </credit>
+
+ <desc>Which tool can I use to create or modify dconf profiles?</desc>
+ </info>
+
+ <title>Editing dconf profiles</title>
+
+ <p>dconf comes with a commandline utility for this purpose, also called
+ <app>dconf</app>. It is very minimal.</p>
+
+</page>
diff --git a/system-admin-guide/C/dconf-profiles.page b/system-admin-guide/C/dconf-profiles.page
index 69e6549..f5b56fa 100644
--- a/system-admin-guide/C/dconf-profiles.page
+++ b/system-admin-guide/C/dconf-profiles.page
@@ -6,28 +6,42 @@
<link type="guide" xref="index" group="user" />
<credit type="author copyright">
- <name>Michael Hill</name>
- <email>mdhillca gmail com</email>
+ <name>Ryan Lortie</name>
+ <email>desrt desrt ca</email>
<years>2012</years>
</credit>
- <desc>Set system-wide default values using dconf's Key File Directories</desc>
+ <desc>Set system-wide default values using dconf's key file directories</desc>
</info>
<title>Custom default values for system settings</title>
- <comment>
- <cite date="2012-05-21" href="mailto:mdhillca gmail com">Michael Hill</cite>
- <p>This assumes the reader knows how to.... By the end of this page,
- the reader will be able to....</p>
- </comment>
+ <p>System-wide default values can be set using dconf's <em>key file
+ directories</em>. These were introduced to support the ability to configure
+ the system with a text editor. For any given system database, a corresponding
+ directory can be created (with <file>.d</file> added to the filename, for
+ example <file>/etc/dconf/db/local.d</file>). This directory contains keyfiles
+ in a special format that can be compiled into the dconf database.</p>
- <p>Short introductory text...</p>
+ <p>A key file in this directory will look something like this:</p>
- <steps>
- <item><p>First step...</p></item>
- <item><p>Second step...</p></item>
- <item><p>Third step...</p></item>
- </steps>
+ <code>
+# Some useful default settings for our site
+
+[system/proxy/http]
+host='172.16.0.1'
+enabled=true
+
+[org/gnome/desktop/background]
+picture-uri='file:///usr/local/rupert-corp/company-wallpaper.jpeg'
+ </code>
+
+ <p>After modifying any key file in one of these directories, the
+ <app>dconf update</app> tool should be run. This tool scans the
+ <file>/etc/dconf/db/</file> directory for databases with corresponding
+ <file>.d</file> directories. If the timestamp on the directory is newer than
+ the one on the file, the file is regenerated. The tool sends a notification
+ on the system D-Bus to all running applications instructing them to re-read
+ their settings.</p>
</page>
diff --git a/system-admin-guide/C/gsettings-browse.page b/system-admin-guide/C/gsettings-browse.page
new file mode 100644
index 0000000..603c665
--- /dev/null
+++ b/system-admin-guide/C/gsettings-browse.page
@@ -0,0 +1,32 @@
+<page xmlns="http://projectmallard.org/1.0/"
+ type="topic" style="task"
+ id="gsettings-browse">
+ <info>
+ <revision version="0.1" date="2012-07-02" status="stub"/>
+ <link type="guide" xref="index" group="tools" />
+
+ <credit type="author copyright">
+ <name>Matthias Clasen</name>
+ <email>matthias clasen gmail com</email>
+ <years>2012</years>
+ </credit>
+
+ <desc>Which tool can I use to explore gsettings?</desc>
+ </info>
+
+ <title>Exploring gsettings</title>
+
+ <comment>
+ <cite date="2012-07-02" href="mailto:mdhillca gmail com">Michael Hill</cite>
+ <p>Adapted from l-g-o SysAdminGuide page. Add a see-also?</p>
+ </comment>
+
+ <p><app>dconf-editor</app> is a graphical utility that lets you browse
+ gsettings. The <app>gsettings</app> commandline utility does the same in a
+ non-graphical way; it has very useful bash completion. Note that these tools
+ always operate on the current user's gsettings database, so you don't want to
+ run them as root. In addition, they require a D-Bus session bus in order to
+ make any changes (since that requires activating the dconf daemon via
+ D-Bus).</p>
+
+</page>
diff --git a/system-admin-guide/C/index.page b/system-admin-guide/C/index.page
index 99b5d1b..29551f2 100644
--- a/system-admin-guide/C/index.page
+++ b/system-admin-guide/C/index.page
@@ -28,6 +28,14 @@
<title>GNOME Desktop System Administration Guide</title>
+<links type="topic" style="toronto" groups="tools">
+ <title>Tools</title>
+</links>
+
+<links type="topic" style="toronto" groups="processes">
+ <title>Processes</title>
+</links>
+
<links type="topic" style="toronto" groups="user">
<title>User settings</title>
</links>
diff --git a/system-admin-guide/C/lockdown.page b/system-admin-guide/C/lockdown.page
index 99694d6..1432052 100644
--- a/system-admin-guide/C/lockdown.page
+++ b/system-admin-guide/C/lockdown.page
@@ -6,28 +6,38 @@
<link type="guide" xref="index" group="user" />
<credit type="author copyright">
- <name>Michael Hill</name>
- <email>mdhillca gmail com</email>
+ <name>Ryan Lortie</name>
+ <email>desrt desrt ca</email>
<years>2012</years>
</credit>
- <desc>Use dconf's Lockdown to prevent users changing specific settings</desc>
+ <desc>Use dconf's <em>lockdown</em> to prevent users changing specific
+ settings</desc>
</info>
<title>Locking down specific settings</title>
- <comment>
- <cite date="2012-05-21" href="mailto:mdhillca gmail com">Michael Hill</cite>
- <p>This assumes the reader knows how to.... By the end of this page,
- the reader will be able to....</p>
- </comment>
+ <p>Use dconf's <em>lockdown</em> to prevent users changing specific settings.
+ Lockdown is supported by creating a <file>locks</file> subdirectory in the
+ keyfile directory (ie: <file>/etc/dconf/db/local.d/locks</file>). The files
+ contained in this directory contain a list of keys to lock, one per line.
+ Just as with the <link xref="dconf-profiles">keyfiles</link>, you may add any
+ number of files to this directory. Here's an example of what one might look
+ like:</p>
- <p>Short introductory text...</p>
+ <code>
+# prevent changes to the company wallpaper
+/org/gnome/desktop/background/picture-uri
+ </code>
- <steps>
- <item><p>First step...</p></item>
- <item><p>Second step...</p></item>
- <item><p>Third step...</p></item>
- </steps>
+ <p><app>dconf update</app> needs to be run after changing the locks. The tool
+ will notice if the timestamp on the <file>locks</file> directory has changed,
+ so there is no need to touch the <file>.d</file> directory as well.</p>
+
+ <note>
+ <p>As of dconf 0.7.4, lockdown is only supported on a per-key basis for
+ performance reasons; you may not yet lock entire subpaths. There are plans
+ to address this in future releases.</p>
+ </note>
</page>
diff --git a/system-admin-guide/C/processes.page b/system-admin-guide/C/processes.page
new file mode 100644
index 0000000..251663e
--- /dev/null
+++ b/system-admin-guide/C/processes.page
@@ -0,0 +1,29 @@
+<page xmlns="http://projectmallard.org/1.0/"
+ type="topic" style="task"
+ id="processes">
+ <info>
+ <revision version="0.1" date="2012-07-02" status="stub"/>
+ <link type="guide" xref="index" group="processes" />
+
+ <credit type="author copyright">
+ <name>Matthias Clasen</name>
+ <email>matthias clasen gmail com</email>
+ <years>2012</years>
+ </credit>
+
+ <desc>Which processes should I expect to see running in a pristine, stock
+ GNOME session?</desc>
+ </info>
+
+ <title>Typical processes</title>
+
+ <p>In a pristine, stock GNOME session, the following processes should be
+ running: dbus-daemon, gnome-session, gnome-shell, gnome-settings-daemon,
+ pulseaudio, gnome-keyring-daemon.</p>
+
+ <p>Depending on the user's setup, you might also see various gvfs processes,
+ goa-daemon, gnome-shell-calendar-server, various evolution factory processes,
+ gsd-printer, gnome-screensaver, at-spi2-dbus-launcher, and at-spi2-registryd,
+ among others.</p>
+
+</page>
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]