thanks for responding.
I managed to solve my problem in the meantime (see my previous mail in
this thread), but I'll make a memo of sshfs and have a look at it.
joerg
On Sat, 10 Nov 2012 21:04:07 +0100, Ramon Ribó <ram...@compassis.com>
wrote:
Hello,
One simple solution, if using Linux, is sshfs. It creates a remote file
system in the local computer. Then, You can sync as if the remote file
were
a local file. It works nicely.
Maybe the fossil ssh implementation can get some ideas from this package.
Ramon Ribó
2012/11/10 Martin Gagnon <eme...@gmail.com>
On Sat, Nov 10, 2012 at 2:18 PM, Richard Hipp <d...@sqlite.org> wrote:
>
>
> On Sat, Nov 10, 2012 at 11:53 AM, Martin Gagnon <eme...@gmail.com>
wrote:
>>
>> On Sat, Nov 10, 2012 at 9:48 AM, Richard Hipp <d...@sqlite.org> wrote:
>> >
>> >
>> > On Sat, Nov 10, 2012 at 9:43 AM, j. van den hoff
>> > <veedeeh...@googlemail.com>
>> > wrote:
>> >>
>> >> I would really appreciate if the ssh issue could get addressed by
the
>> >> developers.
>> >
>> >
>> > It has my attention. I just don't know what to do about it. Do
you
>> > have
>> > any suggestions on how to improve the way the SSH method operates?
>> >
>>
>> I think someone have proposed the ideal solution previously in this
>> list (I didn't find it on the mailing list archive, yet)
>>
>> It would be to execute directly fossil throught ssh with a new fossil
>> command which would act similar as "fossil test-http", except that it
>> would process all chunks of sync data until the whole sync/push/pull
>> is completed.
>
>
> http://www.fossil-scm.org/fossil/artifact/935bc0a983135b?ln=192
>
> That's what the current code does. Any ideas on how to make it more
robust
> in the face of varying SSH implementations?
>
I think the problem is that now, it use the shell, it doesn't call
fossil on the remote side directly from the ssh command line.
To be more robust, the test-http command (more precicely the new
command I call ssh-http in my example) should be append to zCmd here:
http://www.fossil-scm.org/fossil/artifact/935bc0a983135b?ln=154
That will connect stdin and stdout *directly* to the remote fossil
command. If you do that, you don't need to care about shell and login
noise. *But* in that case, fossil on remote side will have to handle
the whole sync operation by himself.. (it's like the ssh-http command
call what test-http does multiple time). (for what I understand from
what test-http does)
[snip]
--
Martin G.
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
