Jeff King <peff@xxxxxxxx> writes: > But these days, people often have several simultaneous sessions open. > They may have multiple ssh sessions to a single machine, or they may > have a bunch of terminal windows open, each of which has a login shell > and will send HUP to its children when it exits. In that case, you have > a meta-session surrounding those individual terminal sessions, and you > probably do want to keep the cache going as long as the meta session[1]. > ... > [1] Of course we have no idea when that meta-session is closed. But if > you have a script that runs on X logout, for instance, you could put > "git credential-cache exit" in it. 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. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html