I'm running openssh-3.7.1_p2-r1, under GNOME 2.4 desktop, and I'll notice that once every few hours, GNOME will have spawned a copy of ssh-agent that is running out of control and taking up as much of my CPU time as it can get. This obviously has a pretty detrimental effect on system performance. :(
Reassign bug back. Reason: Hardened herd does not maintain ssh/ssh-agent/desktop.*
you'll probably want to be taking hardened out of the metadata.xml file for openssh then.
Reassigning
I don't really follow, gnome doesn't just spawn ssh-agent processes ?
Yeah it does. etc/X11/Sessions/Gnome : sshagent=`which ssh-agent` if [ -n "$sshagent" ] && [ -x "$sshagent" ] && [ -z "$SSH_AUTH_SOCK" ]; then command="$sshagent -- $command" fi it will do that to get a session parent to include, lets all of gnome fall back to a single ssh-agent. However, as of the moment nothing much -uses- it (nautilus ssh:// ) and I can't reproduce the behaviour you state here either.
I have had it happen a couple of more times, but not with the same regularity it used to under GNOME 2.4.0. (I'm at 2.4.1 now, I think). If I can determine how to reproduce it, I'll let you guys know, but I imagine it's probably triggered by a buggy GNOME situation that's all but resolved now.
Looks like I'm running GNOME 2.4.2 now, actually.
I've this problem too. I am using gnome-2.6.0 (some 2.6.1) I have this problem when i reboot and login to gnome.... It's really annoying because i've to kill it each time! (otherwise everything goes very slow...)
I've detected (maybe but 90% sure) what causes the problem. The problem only occurs with entrance (enlightenment) as login manager, can someone check this please? Last cvs of entrance doesn't work, that's why I've switched back to gdm and the problem dissappeared. I hope there will be some response here now :-s Note: gnome does spawn ssh-agent, but this is normal. But when using entrance, ssh-agent begins to grabbing cpu time....
That would be consistent with what I say as well. I never thought of the connection to entranced, but that is definately consistent with the problems I was having. I'm changing the subject of this bug to reflect this new info, and hopefully I'll be able to test a newer version of entrance later this week.
seems the latest version of ssh-agent fixes this bug please upgrade to it and re-open if i'm wrong :)