On 11/4/15, Rolf Ade <[email protected]> wrote: > > > Updating from my local build 1.32 (which works fine) to a local build > (but not necessary with the same configure options) 1.34 I now get > > <p class="generalError"> > cannot locate home directory - please set the FOSSIL_HOME or HOME > environment variables > </p> > > from fossil using in a cgi script. What changed? And the variables of > which environment? To which value?
Fossil is trying to locate the "~/.fossil file that contains your global settings. I don't know why it is trying to do this. On the https://www.fossil-scm.org/fossil website (which also runs as CGI) the HOME environment variable is set to /root, but no such directory exists within the chroot jail in which Fossil is running. In the CGI script itself, you can add lines like this: setenv: HOME /some/path Which will cause the HOME environment variable to be set to something. But, again, I don't understand why you need it. If you can figure out what is going wrong, we'd appreciate it if you would report your findings. > > rolf > > _______________________________________________ > fossil-users mailing list > [email protected] > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- D. Richard Hipp [email protected] _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
