Under the hood
Useful2 Signal2
A corrupt or huge daemon config file is refused rather than overwritten.
What's wrong with this entry?
Anonymous. No account, no email.
What
Reading the daemon config now classifies the result as text, absent, refused, failed or thrown. A device-node, directory, too-large-for-the-filesystem error, or content over 1 MiB counts as a refusal that aborts the read-modify-write rather than overwriting the file. This applies on the newer storage read path only.
Evidence
is not a regular file (or exceeds 1MiB); refusing read-modify-write
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.223
Daemon lock can now live in the v5 storage backend
Both mention daemon
-
v2.1.246
Background daemon start failures are classified, and a sleeping machine gets one retry
Both mention daemon
-
v2.1.248
Background daemon can retire a same-version instance
Both mention daemon