A refused messaging socket directory now names the exact path component rejected.
What's wrong with this entry?
When the messaging sockets directory cannot be set up safely, the log line now names the specific path component that was refused, and the failure is recorded with a detail field alongside the existing socket_dir_refused cause. Cross-session messaging is still switched off for the session when this happens.
cross-session messaging is OFF for this session
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.234
Messages injected by a host are classified separately from peer messages
Both mention cross
-
v2.1.234
Cross-session control requests check ids more carefully
Both mention cross
-
v2.1.234
Notice acks now wait for the record to persist
Both mention cross