This has probably come up before, but given the number of times this seems to happen, I would suggest that if Mnemosyne 2.0 still saves and backs up upon exiting, that it:
1) Back up before closing the window/GUI 2) Flush/fsync after backing up (and before window closes). On python you can do (2) with os.fsync, although some OSes and filesystems may not support it. This will at least help the people that close Mnemosyne and immediately rip out their USB key or whatever. -- Ben Escoto ----------------- Original message ----------------- From: Jesse <[email protected]> To: [email protected] Date: Sun, 13 Sep 2009 10:55:13 -0600 2009/9/13 Chris <[email protected]> > > Ahh, I should have specified that I am running a Mac. Nothing appears > to be wrong here on my end. > > My log looks like this: > 2009-09-13 10:34:29 : Saved database 0 0 450 > 2009-09-13 10:34:29 : Program stopped > 2009-09-13 10:34:32 : Program started : Mnemosyne 1.2.1 posix darwin > 2009-09-13 10:34:32 : Loaded database 0 0 450 > > > > Chris: Are you closing Mnemosyne before you shut down your Mac? Not sure how session management works on OS X, but it may not be shutting down Mnemosyne cleanly. Since Mnemosyne 1.x only saves on a clean exit, this might cause the problems you're seeing. -- Jesse Weaver --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "mnemosyne-proj-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/mnemosyne-proj-users?hl=en -~----------~----~----~----~------~----~------~--~---
