You'll notice
Useful2 Signal1
Failing to bind the messaging socket now names the cause: path too long, in use, or permissions.
What's wrong with this entry?
Anonymous. No account, no email.
What
Failing to bind the peer-messaging socket at startup now produces a message specific to the cause: a path too long for a Unix socket (roughly 104 bytes), an address already in use, or a permissions problem. A separate error covers the case where the bind works but the setup after it fails.
Details
- The too-long case tells you to choose a shorter path.
- Applies to the error path only; successful startup is unchanged.
Evidence
the path is too long for a Unix socket (max ~104 bytes); choose a shorter one
Strings lifted out of the shipped bundle, so the claim above can be checked against them.