Hang at commit time when using sftp or bzr+ssh
Stephen AuYeung
stephen at ck12.org
Wed Dec 7 17:14:07 UTC 2011
Thanks, John.
Could it be that it works for most because most are using bzr instead of bzrlib directly? Our situation could be different in that we have a process dedicated to perform bzr operations so there could be countless number of commits from the same process.
Do you also know the reason for multiple ssh processes running? I found the number going up and down and not just keep increasing.
Thanks,
Stephen
-----Original Message-----
From: John Arbash Meinel [mailto:john at arbash-meinel.com]
Sent: Wednesday, December 07, 2011 9:04 AM
To: stephen at ck12.org
Cc: 'Martin Pool'; bazaar at lists.canonical.com
Subject: Re: Hang at commit time when using sftp or bzr+ssh
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 12/7/2011 5:22 PM, Stephen AuYeung wrote:
> One suggestion on the ControlMaster setting: Could bzr use the “-S
> none” option when invoking ssh to disable connection sharing? This
> way, it will not be depending on client settings.
>
>
>
> Thanks,
>
> Stephen
*usually* bzr should use connection sharing if someone has set it up, because then we don't have to do the connection handshake for every bzr operation.
I don't know why it isn't working for you, but we really wouldn't want to use -S none ourselves. (I know of at least one person who is using it quite happily.)
One option would be to create a Host entry in your ssh_config file that would be specific to bzr. Something like:
Host bzr-foo
Hostname real-name.com
ControlMaster None # or whatever the setting is
And then for bzr instead of doing:
bzr branch bzr+ssh://real-name.com/path
you would do
bzr branch bzr+ssh://bzr-foo/path
John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk7fnGsACgkQJdeBCYSNAANQMwCgwfiN0vx326hZVCURMibyovz0
rgAAnRxcpIbBG4QwDJquKgqHkE6KGbbc
=jzeh
-----END PGP SIGNATURE-----
More information about the bazaar
mailing list