I have recently deployed sqlite 3.6.4 as a replacement for a mirrd database. I am only opening a single database connection on a single-threaded process. The process is built and run two ways, natively compiled on an x86 linux system, and cross-compiled using DENX's ELDK to run on a powerpc-6xx linux system.
Everything works fine except that on the ppc system, the process that has the database connection forks a child process as a result of calling sqlite3_open_v2. I can't tell exactly what the child process is doing, but it seems to be nothing much. strace tells me that it repeatedly calls 'getppid' and 'select' and nothing else. Killing the child leaves a zombie process but has not effect on the operation of the parent process. My code does not contain any variant of fork or clone, and neither does the sqlite code. Does anyone have any idea why the child process is created and if there is any way to prevent it? Tanks in advance, Logan Ratner | Software Engineer | Gas Chromatographs Emerson Process Management | 5650 Brittmoore Road | Houston | TX | 77041 T +1 713 827 3807 | F +1 713 827 6313 | logan.rat...@emerson.com <mailto:logan.rat...@emerson.com> | www.EmersonProcess.com <http://www.emersonprocess.com/> _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
