Oops, I was a bit quick on the trigger -- $SSH_AUTH_SOCK points directly to the socket, not to the directory containing it. :-( The correct workaround is as follows (i.e., this is a correction to comment #9 above):
/usr/bin/gnome-keyring-daemon --start newsockdir=`ls -dt1 /tmp/keyring* | head -1` rm -rf $SSH_AUTH_SOCK ln -s $newsockdir `dirname $SSH_AUTH_SOCK`
As Bullwinkle would say, "this time for sure". :-)
Oops, I was a bit quick on the trigger -- $SSH_AUTH_SOCK points directly to the socket, not to the directory containing it. :-( The correct workaround is as follows (i.e., this is a correction to comment #9 above):
/usr/bin/ gnome-keyring- daemon --start
newsockdir=`ls -dt1 /tmp/keyring* | head -1`
rm -rf $SSH_AUTH_SOCK
ln -s $newsockdir `dirname $SSH_AUTH_SOCK`
As Bullwinkle would say, "this time for sure". :-)