git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Is there a reason the credential cache server cowardly refuses to delete/reuse the socket file?

From
Jeff King <peff@peff.net>
Date
Jun 15, 2014, 14:08 UTC
Message-ID
<20140615140800.GA6216@sigill.intra.peff.net>
In-Reply-To
<1EFC4B213D584B1EBAE78E6882705B6D@black>
On Sun, Jun 15, 2014 at 09:48:24AM -0400, Jason Pyeron wrote:
> Whenever my computer crashes, I am left with a socket file. On next git
> invocation it tries to conenct to the file, but the daemon is not running so it
> barfs until I delete the file.

It's supposed to transparently handle this situation. The server always runs unlink() before binding to clear it out. The client will spawn the server when it tries to connect and gets either ENOENT or ECONNREFUSED.

But:
> jpyeron@black /projects/dcarr/saar
> $ git push
> fatal: unable to connect to cache daemon: No error

Apparently your errno is 0 after returning an error from credential-cache.c:send_request?

Could this be a cygwin weirdness? I'd be interested to see the output of:

  echo url=https://example.com |
  strace -f git credential-cache get
in such a case.
-Peff
Previous: Jason PyeronNext: Jason Pyeron
Message 2 of 5 in “Is there a reason the credential cache server cowardly refuses to delete/reuse the socket file?”
  1. Jason PyeronJun 15, 2014
  2. Jeff KingJun 15, 2014
  3. Jason PyeronJun 15, 2014
  4. Jason PyeronJun 15, 2014
  5. Jeff KingJun 17, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.