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

Re: git-credential-cache--daemon quits on SIGHUP, can we change it to ignore instead?

From
Noam Postavsky <npostavs@users.sourceforge.net>
Date
Oct 28, 2015, 03:46 UTC
Message-ID
<CAM-tV--B3HaC1DcORfnx9bWW9-quyk0=pQDxmvonc=6dgrMOxA@mail.gmail.com>
In-Reply-To
<20151027184702.GB12717@sigill.intra.peff.net>
On Tue, Oct 27, 2015 at 2:47 PM, Jeff King <peff@peff.net> wrote:
Show 13 quoted lines
> On Tue, Oct 27, 2015 at 10:52:52AM -0700, Junio C Hamano wrote:
>> Yes.  Probably the right way forward is to make it a non-issue by
>> teaching users how to control the lifetime of the "daemon" process,
>> and wean them off relying on "it is auto-spawned if you forgot to
>> start", as that convenience of auto-spawning is associated with
>> "...but how it is auto-shutdown really depends on many things in
>> your specific environment", which is the issue.
>
> I dunno. I think the auto-spawn is really what makes it usable; you can
> drop it in with "git config credential.helper config" and forget about
> it. Anything more fancy requires touching your login/startup files.
> Certainly I'm not opposed to people setting it up outside of the
> auto-spawn, but I wouldn't want that feature to go away.

Perhaps we could express the auto-spawn more explicitly, something like "git config credential.pre-helper start-cache-daemon". A way to run a command before the credential helpers start would be useful to our magit workaround for this issue (currently we start the daemon before "push", "fetch", and "pull", but it won't work with user aliases that run those commands).

Show 5 quoted lines
>
> I am a little surprised that credential-cache gets wide use. I would
> think most people would prefer to use a system-specific secure-storage
> helper. I don't know what the state of the art is for that on Linux[1], but
> we seem to have only gnome-keyring in contrib/.

I'm not sure it's that widely used. Perhaps most people use ssh-agent? That's what I do, though I've been experimenting with credential-cache since it was brought up by a magit user.

Previous: Jeff KingNext: Jeff King
Message 14 of 29 in “git-credential-cache--daemon quits on SIGHUP, can we change it to ignore instead?”
  1. Noam PostavskyOct 10, 2015
  2. Noam PostavskyOct 18, 2015
  3. Junio C HamanoOct 18, 2015
  4. Noam PostavskyOct 19, 2015
  5. Noam PostavskyOct 21, 2015
  6. Noam PostavskyOct 24, 2015
  7. Junio C HamanoOct 25, 2015
  8. Jeff KingOct 26, 2015
  9. Noam PostavskyOct 27, 2015
  10. Jeff KingOct 27, 2015
  11. Junio C HamanoOct 27, 2015
  12. Junio C HamanoOct 27, 2015
  13. Jeff KingOct 27, 2015
  14. Noam PostavskyOct 28, 2015
  15. Jeff KingOct 30, 2015
  16. Noam PostavskyOct 30, 2015
  17. Jeff KingOct 30, 2015
  18. Noam PostavskyOct 30, 2015
  19. Jeff KingOct 30, 2015
  20. Noam PostavskyNov 9, 2015
  21. Jeff KingNov 9, 2015
  22. Noam PostavskyNov 10, 2015
  23. Jeff KingNov 10, 2015
  24. Jeff KingNov 10, 2015
  25. Noam PostavskyNov 11, 2015
  26. Junio C HamanoDec 4, 2015
  27. Jeff KingDec 4, 2015
  28. Junio C HamanoDec 4, 2015
  29. Jeff KingDec 4, 2015

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.