1 The effect of "disorder reconfigure"
2 ====================================
4 This is current rather vaguely defined and implemented. This file
5 will lay out what you can and cannot change over a reconfigure. Any
6 other changes will require a full server restart.
8 The situation is gradually improving; this file tracks the current
11 * Options that might have to remain the same across restart
13 Arguably if there is anything in this section then that's a serious
16 ** alias (enforced at reload only)
18 This defines how aliases are inserted into the track database. Need
19 to think about how changing it will affect things.
21 ** namepart (enforced at reload only)
23 Probably affects alias construction.
25 ** stopword (enforced at reload only)
27 The search database will have to be rebuilt from scratch.
29 ** user (enforced at reload only)
31 All the files will be owned by the wrong user!
33 * Options that must remain the same across reload
35 Some things will just require a restart. We should either enforce
36 this (refusing to accept modified configurations that purport to
37 change them) or explicitly ignore it.
39 ** home (enforced at reload)
41 We absolutely cannot accept changing our state directory.
43 ** lock (generates a deprecation warning)
45 Liable to be removed anyway.
47 ** nice_speaker (generates a warning)
49 You can't renice a running speaker to make it less nice (and we don't
50 try to make it more nice).
52 * Options that ought to be changable across reload but aren't
54 These options need some work somewhere to be changeable just by a
59 The main server will cope fine with this changing. The speaker will
60 ignore the change however.
64 The speaker will ignore the change.
68 The speaker will ignore the change.
72 If the set of collections change we ought to initiate a rescan.
76 The speaker will ignore the change.
80 The speaker will ignore the change.
84 The speaker will ignore the change.
88 The speaker will ignore the change.
92 The speaker will ignore the change.
96 The speaker will ignore the change.
98 * Options that can be changed across reload
100 These options can be changed at reload and it should just work.
102 ** authorization_algoritm
120 Wouldn't affect an already-running rescan, but reload already cancels
121 and restarts the underway rescan anyway.
137 * Options that can change, but with a caveat
139 These options can be changed at reload but there is some caveat about
140 this (which ought to be documented, and in some cases is).
144 Plugin path. You can change the plugin path but an already-loaded
145 plugin may stay loaded.
147 ** cookie_key_lifetime
149 Only affects subsequently generated keys - cannot shorten (or extend)
150 the lifetime of the current key.
152 ** cookie_login_lifetime
154 Only affects subsequently generated cookies - cannot shorten (or
155 extend) the lifetime of already-generated cookies.
159 The history might not shorten until it's next written.
163 Won't affect running players or decoders.
167 Won't shrink the queue.
171 Won't affect already-computed lengths.
173 * Implementation Considerations
175 A likely change is that the speaker will be created on demand and
176 stopped when idle. Some changes will still be handled via SM_RELOAD
177 but others may require the speaker to quit and restart.