The problem on Win7 seems to be that if the Windows build of fossil.exe tries to use a Cygwin build of ssh.exe, it cannot invoke the ssh.exe executable (fossil.exe says "cannot create child process"). A Cygwin build of fossil.exe seems to work fine with Cygwin's ssh.exe.
Is this a known problem? The same behavior occurs with the ssh.exe that's packaged with the Windows version of Git. That executable does not appear to need cygwin.dll, though. So now I don't know what exactly is going on, except that using Cygwin builds together works OK. Thanks, - Joe On Thu, Apr 9, 2015 at 2:31 PM, Joe Knapka <[email protected]> wrote: > Hello all, > > Thank you, Andy and Ron, I can now clone and sync from my Linux client. My > colleague who is attempting this from his Win7 machine is not having so > much luck. (Actually it's me with a Win7 machine, but I'm trying to figure > it out so I can concisely tell my colleague how to do it on his Win7 > machine.) > > The problem is that I have an ssh.exe (Cygwin's) that is not on my default > PATH, and I don't really want to have Cygwin's bin directory on my regular > path anyway - I start a Bash shell when I want to do Cygwin things. So I > try this (using a fresh fossil 1.32 for Windows that I downloaded five > minutes ago): > > fossil clone ssh://me@server/repo.fossil?fossil=/home/me/bin/fossil > local-repo.fossil --ssh-command=C:\cygwin\bin\ssh.exe > > This results in: > > unrecognized command-line option, or missing argument: > --ssh-command=C:\cygwin\bin\ssh.exe > > I cannot find any documentation for the --ssh-command option mentioned > up-thread. Have I got the syntax wrong? > > Suggestions? > > Thank you again, > > - Joe > > > > On Thu, Apr 9, 2015 at 10:43 AM, Andy Bradford <[email protected]> > wrote: > >> Thus said Ron W on Thu, 09 Apr 2015 11:55:14 -0400: >> >> > Also note that the SSH command to be used can be specified by the >> > --ssh-command= option. (But the fossil= URL parameter is easier in >> > this situation.) >> >> The two options are not really related. >> >> The --ssh-command option does not define the remote command, it defines >> the local SSH command and any command line options that will be run to >> setup the SSH connection to the remote host. e.g., >> >> ssh -T -e none -vvv -i /key etc... >> >> The fossil= query parameter defines the remote fossil command that will >> be run via SSH. It defaults to simply ``fossil http'', however, if the >> remote host does not have fossil in a standard path you'll get an error >> like ``fossil: command not found.'' >> >> Thanks, >> >> Andy >> -- >> TAI64 timestamp: 400000005526ac6c >> _______________________________________________ >> fossil-users mailing list >> [email protected] >> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >> >> > > > -- > It is always best to think of reality as perfectly normal. Since the > beginning, not one unusual thing has ever happened. - Less Wrong > -- It is always best to think of reality as perfectly normal. Since the beginning, not one unusual thing has ever happened. - Less Wrong
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
