mirror of
https://github.com/fish-shell/fish-shell
synced 2024-12-27 21:33:09 +00:00
Fixes misleading "connect: Connection failed" message on start up
When launching the first instance of fish and fishd is not launched already, this should not be considered an error as long as it can be launched. So ignore the first failure of connect(), as the calling function get_socket() will try again. May need a bit of cleanup.
This commit is contained in:
parent
14b6d32fe6
commit
cfbb511d26
1 changed files with 6 additions and 1 deletions
|
@ -132,7 +132,12 @@ static int try_get_socket_once(void)
|
||||||
if (connect(s, (struct sockaddr *)&local, sizeof local) == -1)
|
if (connect(s, (struct sockaddr *)&local, sizeof local) == -1)
|
||||||
{
|
{
|
||||||
close(s);
|
close(s);
|
||||||
|
|
||||||
|
/* If it fails on first try, it's probably no serious error, but fishd hasn't been launched yet.
|
||||||
|
This happens (at least) on the first concurrent session. */
|
||||||
|
if (get_socket_count > 1)
|
||||||
wperror(L"connect");
|
wperror(L"connect");
|
||||||
|
|
||||||
return -1;
|
return -1;
|
||||||
}
|
}
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue