On Tue, 31 Oct 2006 [EMAIL PROTECTED] wrote:
I suspect that the /var/tmp file is unrelated to your mmap/munmap problem.
When SQLite needs a temporary file on Unix, it creates the file, opens it,
then calls unlink(). Unix removes the inode for the file from its directory
immediately so that the file cannot be opened again by another process. But
it does not delete the file until the file descriptor is closed. This is
how you make temporary files in Unix that automatically disappear when they
are closed.
right - that makes sense then...
SQLite never calls mmap() or munmap() - at least not directly. Those
routines might be called in your implementation of malloc() or as part of
open()/read()/write(). But if so, that is an implementation specific thing.
hmmm. most likey malloc - also, this kernel uses mmap to read in binaries and
the specific amount of memory being asked for is quite large.
in any case, i'll work on the assumption that sqlite is not at fault.
thanks very much for the fast reply - and for a fantastic product.
btw. this is what my software does with it
http://www.linuxjournal.com/article/7922
cheers.
-a
--
my religion is very simple. my religion is kindness. -- the dalai lama
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
