It may be worth mentioning in the CGI setup instructions that Fossil/sqlite needs to be able to create temporary files for rollback logs in some manner particular to the OS, such as by writing to /tmp.
In my case, I installed Fossil according to the standard chroot procedure in OpenBSD for CGI applications, by placing the CGI script in /var/www/cgi-bin. Sqlite failed to create a temporary file and attempted to create one in the script's current working directory, (/var/www)/cgi-bin before failing. The error message suggested that Fossil needed write access to the /cgi-bin directory. This is a bad idea. I was able to get Fossil to work correctly by providing (/var/www)/tmp. The current permissions requirements state: - The Fossil binary must be readable/executable, and ALL directories leading up to it must be readable by the process which executes the CGI. - ALL directories leading to the CGI script must also be readable and the CGI script itself must be executable for the user under which it will run (which often differs from the one running the web server - consult your site's documentation or administrator). - The repository file AND the directory containing it must be writable by the same account which executes the Fossil binary (again, this might differ from the WWW user). The directory needs to be writable so that sqlite can write its journal files. Regards, Paul Pereira
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
