rpc: ensure daemon is spawn even if dead socket exists
The auto-spawn code would originally attempt to spawn the daemon for both ENOENT and ECONNREFUSED errors from connect(). The various refactorings eventually lost this so we only spawn the daemon on ENOENT. The result is if the daemon exits uncleanly, so that the socket is left in the filesystem, we will never be able to auto-spawn the daemon again. (cherry picked from commit 406ee8c2)
Showing
想要评论请 注册 或 登录