This might be slightly off topic, but perhaps a common problem for many sqlite users.
I have a database (wal mode) that apache (the web server) needs to access, readonly. Since it needs to be able to lock it for reading, apache needs write access. So the database has these permissions: -rw-rw-r-- 1 user apache 1837704192 2012-04-22 09:58 database.db The directory is also group writeable. The trouble is that when apache is accessing the database, the database file owner can't access it, not even for reading. The result is "unable to open database file". I believe that the cause is that apache creates these files: -rw-r--r-- 1 apache apache 32768 2012-04-22 10:15 database.db-shm -rw-r--r-- 1 apache apache 0 2012-04-22 09:58 database.db-wal which other users have no write access to. So access to the database is locked until sqlite remove these files. Is there a way to work around this, other than to set umask 002 for apache? -- Steinar _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
