diff options
| author | 2026-05-22 10:41:24 +0100 | |
|---|---|---|
| committer | 2026-05-22 10:41:24 +0100 | |
| commit | 982d180f9b9a2f8a90d454816474dce8d4b4b8e2 (patch) | |
| tree | f21a97bbb74eca554775b37fb9faed23bbbfd315 /dot_claude/skills/tuicr | |
| parent | 6b7e057bd4fc2cbdffe5fc8b3095810db1ccf9e3 (diff) | |
| download | dotfiles-982d180f9b9a2f8a90d454816474dce8d4b4b8e2.tar.gz dotfiles-982d180f9b9a2f8a90d454816474dce8d4b4b8e2.tar.bz2 dotfiles-982d180f9b9a2f8a90d454816474dce8d4b4b8e2.zip | |
fix(ssh): make agent.sock symlink concurrent-connection-safe
Previously every new login retargeted ~/.ssh/agent.sock to its own
per-connection forwarded socket. That broke a multi-connection setup
when the most-recent connection (which 'won' the symlink) dropped:
all surviving connections' panes would point at a dead socket until a
fresh login from a surviving connection re-ran zprofile.
zprofile: only retarget when the existing symlink target is dead
(sshd unlinks the per-connection socket on disconnect, so [[ -S ]] on
the resolved path is a reliable liveness probe). First connection
seeds the symlink, subsequent logins keep using it.
ssh-agent-refresh: scan /tmp/ssh-*/agent.* for any live forwarded
socket and retarget to the first that responds to ssh-add. Lets the
surviving connection recover without waiting for a new login shell.
Diffstat (limited to 'dot_claude/skills/tuicr')
0 files changed, 0 insertions, 0 deletions
