Changes between Version 1 and Version 2 of EditingConfigurationParameters

Timestamp:

Jan 22, 2010, 2:54:27 PM (12 years ago)

Author:

kim

Comment:

--

EditingConfigurationParameters

@@ -6 +6 @@
 Note: The client ''should'' be shutdown before making changes, otherwise settings will be reverted to it's previous state.
 
-== Transmission-Desktop Linux/GTK, Qt, Transmission-Server ==
+== Transmission-Desktop Linux/GTK, Qt, Transmission-Daemon ==
 
 GTK, CLI and Daemon (both on a Mac and Linux) use a [http://www.json.org/ JSON] formatted file, mainly because of its human readability. [[BR]]
@@ -13 +13 @@
 === Reload Settings ===
 You can make the daemon reload the settings file by sending it the {{{SIGHUP}}} signal.[[BR]]
-Or, simply run either of the following commands:
+Eg:
 {{{
 $ killall -HUP transmission-daemon
-}}}
-Or:
-{{{
-$ pkill -HUP transmission-daemon
 }}}
 However bear in mind that if you edit settings whilst the daemon is running they may be overwritten.
 
 === Formatting ===
-Here is a sample of the three basic types, respectively Boolean, Number and String:
+There are three basic types:
+
+
+|| '''Type''' || '''Values''' ||
+|| Boolean || true, false ||
+|| Number ||  Integer or Real depending on context ||
+|| String || surround with (double?) quotes ||
+
+The settings.json format is:
+{{{
+    "KEY"  :  VALUE,    (for a Boolean or Number)
+    "KEY"  :  "VALUE"   (for a string)
+}}}
+
+Example:
 {{{
 {
-    "rpc-enabled": 1,
+    "rpc-enabled": true,
     "peer-port" : 51413,
     "rpc-whitelist": "127.0.0.1,192.168.*.*"