On Thu, 14 Jun 2012 14:42:48 -0700 Brian Smith <[email protected]> wrote:
> I had success with this line to execute fossil: > /usr/bin/env -i HOME=$(pwd) /usr/local/bin/fossil ls 2>&1 It runs fossil with the same success as the simple "fossil ls --nocgi" -> "not within an open checkout" > 4) env -i erases the complete environment, your issues were caused by > fossil believing that it was executing as a CGI, when really > you just wanted to happen to call it from a CGI - If I've read this thread > correctly. No, --nocgi option solves this problem. Fossil does not acts as a cgi. For example "fossil help" outputs the help to the stdout. Fossil simply can't see the open checkout where it is running. It maybe is because of environment, because of access permissions, because of bugs, etc. I can't diagnose the cause for this behaviour. Very similar script in Windows (.cmd file) runs OK. > !!!! 5) This script rings all sorts of alarm bells for me. I hope you plan > on restricting access via IP and/or at least basic authentication. > Bash is well tested - but was not really meant to be exposed to the open > internet, one wrong move and you could give someone > the keys to your machine without realizing it. I know the risks, but if the script is simple enough, the risks are less. Actually, I plan to implement the same functionality in assembly language later. I only try to proof the concept with these bash scripts... unsuccessfuly. -- John Found <[email protected]> _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
