> The kernel grants them: http://www.manpagez.com/man/2/flock . Or I > might use fcntl().
That's why I've asked what is different here from what SQLite already does because SQLite uses fcntl() on database file already. You can try to change it to flock() of course but be aware that SQLite needs more lock grades than flock() provides. Pavel On Fri, Sep 18, 2009 at 1:07 PM, Angus March <an...@uducat.com> wrote: > Pavel Ivanov wrote: >> >>> To be clear, my idea of blocking is as follows: if one tries to >>> achieve a lock, and it is not possible, the request is put into a queue, >>> and the caller stops consuming cycles. Locks are then granted (when >>> feasible) in the queue in the order that they were requested. >>> >> >> The problem is who will grant these locks? You want to launch some >> separate process which will contain information about all processes >> requested locks and will communicate somehow with these processes to >> tell them that they can continue in acquiring the lock? >> >> > The kernel grants them: http://www.manpagez.com/man/2/flock . Or I > might use fcntl(). > > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
