Public bug reported:
I (and everybody on my team) have a list of 36 bzr repositories we pull
in as source deps of our project. As updating them all is very slow,
mostly due to network latency, we update them in parallel, 10 at a time,
using xargs. Something like
$ xargs -n1 -P10 ./update-repo.sh < sourcedeps.txt
where update-repo.sh does cd $1 && bzr pull, and bzr uses ssh-agent to
get the ssh keys, and this is where you come in :) because since we
moved to jaunty, we're killing ssh-agent every single time we do this.
Not actually killing it; it simply stops responding: suddenly we get
these bzrs asking for the passphrase (and failing, obviously). And,
$ ssh-add
Could not open a connection to your authentication agent.
but ssh-agent is still there,
$ ps -C ssh-agent www
PID TTY STAT TIME COMMAND
3208 ? Ss 0:00 /usr/bin/ssh-agent /usr/bin/gpg-agent --daemon
--sh --write-env-file=/home/john/.gnupg/gpg-agent-info-watermeal
/usr/bin/dbus-launch --exit-with-session /usr/bin/pulse-session
/usr/bin/seahorse-agent --execute x-session-manager
Thanks,
** Affects: openssh (Ubuntu)
Importance: Undecided
Status: New
--
ssh-agent stops responding
https://bugs.launchpad.net/bugs/352154
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
