While using SQLite as FastCGI module from within PHP-scripts, sometimes I'm
getting error messages, like:

(mod_fastcgi.c.2551) FastCGI-stderr: PHP Warning:
 sqlite_open() [<a href='function.sqlite-open'>function.sqlite-open</a>
 malformed database schema - unable to open a temporary database file
 for storing temporary tables in /usr/local/www/index.php on line 25

Yes, I've found several "recipes", how to fix it, like:

http://hostprogressive.com/support/php_5_docs/ref.sqlite.html

"On Windows operating systems, unprivileged accounts don't have the TMP
environment variable set by default. This will make sqlite create temporary
files in the windows directory, which is not desirable. So, you should set
the TMP environment variable for the web server"

or f.e.:

http://www.bacula.org/dev-manual/Installin_Configuri_SQLite.html

"this is most likely caused by the fact that some versions of SQLite attempt
to create a temporary file in the current directory"


...but the problem is, that:

1. This isn't any Windows-based installation - it's NetBSD.

2. The error message didn't tell, WHERE exactly it's trying to "open a
   temporary database file" - but under NetBSD, lighttpd is working with
   root privileges (the privileges seem not to be dropped, because I can
   see, that the files sent via http form are saved with root.wheel owner).
   So, even if it's trying to create any temporary file, it's able to create
   it anywhere. In /tmp or anywhere else.

3. The problem isn't occuring in regular manner - f.e. once in two weeks
   (while the PHP scripts, which are calling SQLite are used each day).
   So, currently no idea, what is causing that.

Any clues?

NetBSD 2.0 (with kernel from 2.0.2), lighttpd and php modules compiled from
2007Q1.
-- 
                                pozdrawiam / regards

                                                Zbigniew Baniewski

-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------

Reply via email to