Heartbeat writes tolerate harmless failures, though a failed pid-file creation still aborts.
What's wrong with this entry?
Session heartbeat touches and pid-file creation and updates now ask the storage backend to write in place, and tolerate benign write failures instead of throwing. A failure to create the pid file still aborts.
publishDiscipline: "inPlace"
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