I have seen documentation that SQLite uses POSIX advisory locks to
implement locking on Unix.

I have an issue in that attempts to operate on a sqlite database on a
Linux file system that has setgid bit (set group ID on execution) set
on the database file (e.g. chmod g+s) causes database operations to
fail (presumably returning SQLITE_BUSY and "database is locked" error
message).

I looked at the fcntl documentation (since fcntl is used to acquire,
release, and test for the existence of record locks), and this
mentioned both advisory locks and mandatory locks.
If mandatory locking is enabled on a file system, then mandatory
locking is enabled on a file by disabling group execute permission on
the file and enabling the set-group-ID permission bit.

Is sqlite supposed to be able to work on a file that has mandatory
locking enabled?
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to