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 I intend to improve the situation, but for now this is how it is.
10 * Options that might have to remain the same across restart
12 Arguably if there is anything in this section then that's a serious
17 This defines how aliases are inserted into the track database. Need
18 to think about how changing it will affect things.
22 Probably affects alias construction.
26 The search database will have to be rebuilt from scratch. This is
27 do-able but AFAIK we don't detect it.
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.
41 We absolutely cannot accept changing our state directory. If this is
42 attempted it must be rejected.
46 Liable to be removed anyway.
50 Can't renice a running speaker to make it less nice (and we don't try
51 to make it more nice). We ought to issue an error message and
54 * Options that ought to be changable across reload but aren't
56 These options need some work somewhere to be changeable just by a
61 The main server will cope fine with this changing. The speaker will
62 ignore the change however.
66 The speaker will ignore the change.
70 The speaker will ignore the change.
74 If the set of collections change we ought to initiate a rescan.
78 The speaker will ignore the change.
82 The speaker will ignore the change.
86 The speaker will ignore the change.
90 The speaker will ignore the change.
94 The speaker will ignore the change.
98 The speaker will ignore the change.
100 * Options that can be changed across reload
102 These options can be changed at reload and it should just work.
104 ** authorization_algoritm
122 Wouldn't affect an already-running rescan, but reload already cancels
123 and restarts the underway rescan anyway.
139 * Options that can change, but with a caveat
141 These options can be changed at reload but there is some caveat about
142 this (which ought to be documented, and in some cases is).
146 Plugin path. You can change the plugin path but an already-loaded
147 plugin may stay loaded.
149 ** cookie_key_lifetime
151 Only affects subsequently generated keys - cannot shorten (or extend)
152 the lifetime of the current key.
154 ** cookie_login_lifetime
156 Only affects subsequently generated cookies - cannot shorten (or
157 extend) the lifetime of already-generated cookies.
161 The history might not shorten until it's next written.
165 Won't affect running players or decoders.
169 Won't shrink the queue.
173 Won't affect already-computed lengths.
175 * Implementation Considerations
177 A likely change is that the speaker will be created on demand and
178 stopped when idle. Some changes will still be handled via SM_RELOAD
179 but others may require the speaker to quit and restart.