Xfce Wiki

Sub domains
 

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
xfce:xfconf:start [2012/04/23 15:53] nickxfce:xfconf:start [2012/04/23 15:56] – [Kiosk Mode] nick
Line 15: Line 15:
  
 ===== Kiosk Mode ===== ===== Kiosk Mode =====
- +System administrators can lock certain values or entire channels to prevent users from changing them.  In this case, the administrator may provide default values that will be used regardless of what may appear in a user-writable configuration file.  If the sysadmin does not wish to provide values, but only wants to lock a channel/property, the application'default fallback value will be used instead
-The Xfconf daemon supports a so-called "kiosk mode" or "lockdown mode" such that certain configuration properties or certain channels can be locked from user modification.  In this case, the locked values are provided by a system administrator in the form of settings file (in the same format as the user'settings files) in a system read-only location+    
- +Locking a channel or property is as simple as creating a configuration file and setting either (and only eitherthe "lockedor "unlockedattribute on <channel> or <property> elements that should be restricted.  This configuration file should be placed in a system location that is read by the daemon (see "File locations" above). 
- +    
- +Both the "locked" and "unlockedattributes take a semicolon-separated list of system user and group names.  User names should be entered as-is, and group names should be entered with an "@" symbol prepended to the group name. 
-===== XML Markup (DTD===== +    
- +The "locked" attribute specifies users and groups who may not modify the property.  The "unlockedattribute specifies users and groups who may modify the property, with other users locked out.  Only one of the two attributes may be specified for a particular channel or property.  If both are present, the "unlocked" attribute is used, and the "locked" attribute is ignored. 
-  <?xml version="1.0encoding="UTF-8"?> +    
-   +Note that <channellocking locks all properties under that channel, but <property> locking locks only the property with the "locked" or "unlockedattribute; none of the sub-properties are locked unless they also contain a "locked" or "unlocked" attribute.
-  <!ELEMENT channel property*> +
-  <!ELEMENT property (property|value)*>  <!-- <value> elems only allowed +
-                                            if type="array" --> +
-  <!ELEMENT value EMPTY> +
-   +
-  <!ATTLIST channel name CDATA #REQUIRED> +
-  <!ATTLIST channel version CDATA #REQUIRED>  <!-- currently "1.0" --> +
-  <!ATTLIST channel locked CDATA #IMPLIED>    <!-- only one of these --> +
-  <!ATTLIST channel unlocked CDATA #IMPLIED>  <!-- two are allowed --> +
-   +
-  <!ATTLIST property name CDATA #REQUIRED> +
-  <!ATTLIST property type (string|uchar|char|uint16|int16|uint|int|uint64|int64|float|double|bool|array|empty) #REQUIRED> +
-  <!ATTLIST property value CDATA #IMPLIED>  <!-- not used if type="array" +
-                                                 or type="empty" --> +
-  <!ATTLIST property locked CDATA #IMPLIED>    <!-- only one of these --> +
-  <!ATTLIST property unlocked CDATA #IMPLIED>  <!-- two are allowed --> +
-   +
-  <!ATTLIST value type (string|uchar|char|uint16|int16|uint|int|uint64|int64|float|double|bool) #REQUIRED> +
-  <!ATTLIST value value CDATA #REQUIRED> +
- +