On Fri, 2005-01-21 at 09:08 +0000, Keith Blow wrote: > JP. > I had already looked there but there was nothing. Actually I did a lot > more testing last night and the behaviour is weird. The original cause > was Evolution just stopped and when I restarted the addressbook was > gone. I've tried overwriting the db file in addressbook/local/system but > it gets overwritten by the new (post crash) version. So it now seems to > me that the new version must be cached somewhere. I've tried stopping > evolution and then: > touch now > start evolution and edit addressbook and then stop evolution > find . -newer now -print > and this reveals either: next to nothing has changed, > addressbook.db.summary has changed or once a temporary directory had > been created when I added a new address book. So is it possible that the > database is being cached in memory by one of the other evolution > processes that is still running when you stop the main process? I'm > going to try shutting down gdm and then overwriting the addressbook file > and then restarting. Wish me luck. > Keith This worked, copying the old addressbook.db and addressbook.db.summary files when all the processes were killed restired the old database.
signature.asc
Description: This is a digitally signed message part
