It's a completely normal rsync setup as far as I know. I set up a shell script to check the integrity of the data base every five minutes using 'pragma integrity_check'. I checked the shell script log and wasn't really sure of what might have been happening the first time it crashed, but the next time, the time looked remarkably familiar to the system rsync time. I uploaded the db file using rsync and rsynced it down and the database was corrupt. I tested this twice with the same result. I disabled live journaling (after reading the Atomic Commit link) and excluded the db and any possible journal from rsync. (I rsync to a remote machine and it could result from having non synced times.) (Thank you for your long explanation.)
Tito Ciuro wrote: > > > I'm curious... did you do anything specific to end with a corrupted > database when using rsync? Would you mind specifying the steps to do > that? > > > -- View this message in context: http://www.nabble.com/sqlite3-datbase-disk-image-malformed-tp22329261p22363689.html Sent from the SQLite mailing list archive at Nabble.com. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
