Thus said "Andy Bradford" on 29 Jun 2013 20:34:07 -0600: > So it seems to think that the server didn't respond, but it surely > looks like it did. Will this approach even work?
Ok, the problem was that the connection was closed (due to missing keep-alive, so SSH closed connection) in xfer.c:client_sync. I was able to workround it by moving the call to transport_global_startup() at the top of the while ( go ) loop, and adding a transport_global_shutdown() at the bottom. This now seems to work, but it seems like it's no the cleanest solution: $ fossil clone --sshserver ssh://amb@localhost//tmp/temp.fossil test.fossil ssh -e none -T amb@localhost Round-trips: 1 Artifacts sent: 0 received: 1 ssh -e none -T amb@localhost Round-trips: 2 Artifacts sent: 0 received: 2 Clone finished with 487 bytes sent, 1119 bytes received Rebuilding repository meta-data... 100.0% complete... project-id: b3fa0981e117c6a57a0850875f58973eec3a6453 admin-user: amb (password is "3c1aaf") But it fails at this point because it doesn't know about the --sshserver option: $ fossil open test.fossil $ touch file $ fossil add file ADDED file $ fossil ci -m test Autosync: ssh://amb@localhost//tmp/temp.fossil ssh -e none -T amb@localhost $ echo $? 141 So somehow it needs to be taught that when autosync'ing, it should use --sshserver. Guess I'll have to leave that for another day... Does this seem like a worthwhile addition? It seems that it would make handling SSH tunneling configurations much easier---no need to worry about parsing interactive shell responses. Thoughts? Thanks, Andy -- TAI64 timestamp: 4000000051cfda10 _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
