On s?, 2003-06-08 at 16:13, Martin Skj�ldebrand wrote: > > > Apparently it *does* work, kind of. > > > I noticed this when I rebooted my computer, and the calendar info was > > > seen - something apparently has to be restarted for this to work as > > > intended. > > > > You got lucky... You could just as well have ended up with a corrupt > > file. > > > > Wombat, the calendar backend of evolution, is not designed to > > have more than one process accessing the calendar file. In fact the > > Wombat is designed to be that one process that does all the accessing of > > the calendar file, no matter how many frontends are running (the > > frontends will mostly be evolution itself and multisync). > > > > The Wombat keeps all the entries in the calendar in memory, only syncing > > changes to disk once in a while (possibly only on shutdown - I haven't > > checked). > > I see. > However, the accounts are on the same machine. My fiancee and I am > sharing the same box, so only one can be logged in at one time. So, it > should be workable in this setup then. > > I tried killing wombat after exiting Evo but still the same thing > happens. Or rather doesn't. A full restart is required to sync the file > between the different Evo-instances. Mayhaps I need to kill all Evo > related processes after logging out? Then I could put that in an account > rc file?
I that case "evolution --force-shutdown" should shut everything down. ./borup _______________________________________________ evolution maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution
