Changes between Version 11 and Version 12 of PrefsOverride

Timestamp:

Oct 6, 2008, 11:39:03 AM (17 years ago)

Author:

davea

Comment:

--

PrefsOverride

@@ -1 +1 @@
 = Preferences override file =
 
-By default, [GlobalPrefs global preferences] and host venue are maintained on a project server, edited via a web interface, and downloaded from the server.
+By default, [GlobalPrefs global preferences] and host venue are maintained on a project server,
+edited via a web interface, and downloaded from the server.
 
-Some people may want to edit preferences locally, modify preferences on a single host, or hardwire the host venue. To accommodate these requirements, BOINC lets you create a 'preferences override file'. This file is read by the core client after it reads the preferences from the server, and it overrides those preferences.
+Some people may want to edit preferences locally, modify preferences on a single host, or hardwire the host venue.
+To accommodate these requirements, BOINC lets you create a 'preferences override file'.
+This file is read by the core client after it reads the preferences from the server,
+and it overrides those preferences.
 
-The preferences override file is named `global_prefs_override.xml`. Its structure as follows:
+The preferences override file is named `global_prefs_override.xml`.
+Its structure as follows:
 
 {{{
 #!xml
 <global_preferences>
-    <mod_time>%d</mod_time>
+    [ <host_venue>X</host_venue> ]
     <run_on_batteries/>
     <run_if_user_active/>
@@ -47 +52 @@
 }}}
 
-{{{
-#!comment Where did [ <host_venue>venue</host_venue> ] come from? I've removed it since it's badly formed XML and I can't find it in the source.
-
-Look in cs_prefs.c where it says:
-// Read global preferences into the global_prefs structure.
-// 1) read the override file to get venue in case it's there
-// 2) read global_prefs.xml
-// 3) read the override file again
-//
-// This is called:
-// - on startup
-// - on completion of a scheduler or AMS RPC, if they sent prefs
-// - in response to read_global_prefs_override GUI RPC
-
-It's the choice of venue that is done there. As you can set GPOs for different venues. 
-
-    string foo;
-
-    retval = read_file_string(GLOBAL_PREFS_OVERRIDE_FILE, foo);
-    if (!retval) {
-                parse_str(foo.c_str(), "<host_venue>", main_host_venue, sizeof(main_host_venue));
-        }
-
-Sadly, the log for the changeset has nothing to do with this change. Foo? I don't take this feature seriously - I'm going to treat it as deprecated.
-}}}
-
-
-NOTE: the above is updated for BOINC 5.10+; see [source:trunk/boinc/lib/prefs.C lib/prefs.C] and [source:trunk/boinc/lib/prefs.h lib/prefs.h] for more information.
-
-If you write a program for editing preferences locally, you'll want to be able to tell a running core client to reread the preferences override file. You can do this using the [GuiRpc#function-read_global_prefs_override read_global_prefs_override()] GUI RPC, or run [BoincCmd boinc_cmd] with the `--read_global_prefs_override` option.
+If you write a program for editing preferences locally,
+you'll want to be able to tell a running core client to reread the preferences override file.
+You can do this using the [GuiRpc#function-read_global_prefs_override read_global_prefs_override()] GUI RPC,
+or run [BoincCmd boinc_cmd] with the `--read_global_prefs_override` option.