Hi Keith and all, On Sun, Dec 17, 2006 at 19:24:04 -0500, Keith Browne wrote: > I've got so many featurelets floating around, I lost track. When I ran > the test earlier, I still had a ~/.darcs/config file containing "pull > disable-ssh-cm". I was using a darcs binary I thought still had the bug > where the config file was ignored, but I must have been mistaken.
Some more notes on this. I just realised that in order for this scheme
to work (the one where you use --disable-ssh-cm, but you configure ssh
to automatically do control master stuff), you must first log in and
leave a connection open. I.e., in one window:
ssh [EMAIL PROTECTED]
and then in another window:
darcs pull --disable-ssh-cm [EMAIL PROTECTED]
Interestingly, I get the same kind of hanging with this setup, which
leads me to think that maybe the problem is not so much how we're using
the control master, but just the control master itself. Another
potentially useful note is that when I hit Ctrl-C in disgust during the
darcs operation, the logged in ssh window prints this:
mm_receive_fd: recvmsg: expected received 1 got 0
Hmm. Case isn't closed, of course. But just wanted to let you know I'm
still looking into it in my slow, confused manner.
Cheers,
--
Eric Kow http://www.loria.fr/~kow
PGP Key ID: 08AC04F9 Merci de corriger mon français.
pgpFbFrjwOWyN.pgp
Description: PGP signature
_______________________________________________ darcs-devel mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-devel
