https://bugzilla.novell.com/show_bug.cgi?id=383353
User vuntz@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=383353#c8
Vincent Untz
In other words if the variables GNOME_KEYRING_PID and GNOME_KEYRING_SOCKET are set, the process for the pid found in GNOME_KEYRING_PID is /usr/bin/gnome-keyring-daemon and we have a valid socket, the ssh-agent should be skipped?
then this piece of code
# # No ssh-agent if a ssh session is already provided by an other agent. # if test -n "$GNOME_KEYRING_PID" -a -S "$GNOME_KEYRING_SOCKET" ; then if test -S "$SSH_AUTH_SOCK" ; then usessh=no fi fi
before setting up ssh-agent should work. The question is if the variable GNOME_KEYRING_SOCKET holds the path to a real socket file.
It does, yes. I'm just not sure you need to check that it's a socket file since it's unrelated to the ssh-agent part of gnome-keyring-daemon. Note that it might make sense to distribute this in the gnome-keyring package and install a file in /etc/X11/xinit/xinitrc.d/ if files there are sourced during the login. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.