You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
setconfig: put vars in separate "config.setconfig" file.
This is neater than appending to some random file: we only do that once
if there's no "include" line to include a ".setconfig" file.
Signed-off-by: Rusty Russell <[email protected]>
Copy file name to clipboardExpand all lines: contrib/msggen/msggen/schema.json
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -32637,9 +32637,9 @@
32637
32637
"description": [
32638
32638
"The **setconfig** RPC command allows you set the (dynamic) configuration option named by `config`: options which take a value (as separate from simple flag options) also need a `val` parameter.",
32639
32639
"",
32640
-
"This new value will *also* be written at the end of the config file, for persistence across restarts (and any old value commented out).",
32640
+
"This new value will *also* be written at the end of the `config.setconfig` file (but see lightningd-config), for persistence across restarts (and any old value commented out if they were set in other config files).",
32641
32641
"",
32642
-
"You can see what options are dynamically adjustable using lightning-listconfigs(7). Note that you can also adjust existing options for stopped plugins; they will have an effect when the plugin is restarted."
32642
+
"You can see what options are dynamically adjustable using lightning-listconfigs(7). Note that you can also adjust existing options for stopped plugins; they will have an effect when the plugin is restarted."
Copy file name to clipboardExpand all lines: doc/lightningd-config.5.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,10 +11,10 @@ DESCRIPTION
11
11
12
12
When lightningd(8) starts up it usually reads a general configuration
13
13
file (default: **$HOME/.lightning/config**) then a network-specific
14
-
configuration file (default: **$HOME/.lightning/testnet/config**). This can
14
+
configuration file (default: **$HOME/.lightning/bitcoin/config**). This can
15
15
be changed: see *--conf* and *--lightning-dir*.
16
16
17
-
Note that some configuration options, marked *dynamic*m can be changed at runtime: see lightning-setconfig(7).
17
+
Note that some configuration options, marked *dynamic* can be changed at runtime: see lightning-setconfig(7): by default this will write to a file called **config.setconfig** in the network-specific lightning directory, unless there is another config file with a name ending in ".setconfig".
18
18
19
19
General configuration files are processed first, then network-specific
20
20
ones, then command line options: later options override earlier ones
Copy file name to clipboardExpand all lines: doc/schemas/lightning-setconfig.json
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -7,9 +7,9 @@
7
7
"description": [
8
8
"The **setconfig** RPC command allows you set the (dynamic) configuration option named by `config`: options which take a value (as separate from simple flag options) also need a `val` parameter.",
9
9
"",
10
-
"This new value will *also* be written at the end of the config file, for persistence across restarts (and any old value commented out).",
10
+
"This new value will *also* be written at the end of the `config.setconfig` file (but see lightningd-config), for persistence across restarts (and any old value commented out if they were set in other config files).",
11
11
"",
12
-
"You can see what options are dynamically adjustable using lightning-listconfigs(7). Note that you can also adjust existing options for stopped plugins; they will have an effect when the plugin is restarted."
12
+
"You can see what options are dynamically adjustable using lightning-listconfigs(7). Note that you can also adjust existing options for stopped plugins; they will have an effect when the plugin is restarted."
0 commit comments