search for: ssh_auth_pid

...t # Note: if SSH_AGENT_PID is set we assume that it is set correctly and # also SSH_AUTH_SOCK is set export SSH_AGENT_PID=`echo $SSH_AGENT_RUNNING | cut -f 1 -d ' '` # Unfortunatly PID in SSH_AUTH_SOCK is not the same as AGENT_PID. # Heuristic: usually it's one less ... typeset -i SSH_AUTH_PID=$SSH_AGENT_PID-1 export SSH_AUTH_SOCK=`ls /tmp/ssh-*/agent.$SSH_AUTH_PID` fi # assume it's has default identity ... fi>> A hint to something similar like this in the manual probably wouldn't reduce ssh-agent adoption... ------- You are receiving this mail because: -------...

...think that: [ -z "$SSH_AUTH_SOCK" ] && eval `ssh-agent -s` [ -z "$SSH_AGENT_PID" ] || ssh-add -l >/dev/null 2>&1 || ssh-add Is as effective and a lot more concise. On the other hand, fragile heuristics like: > export SSH_AUTH_SOCK=`ls /tmp/ssh-*/agent.$SSH_AUTH_PID` have no place in our documentation. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.