[Evolution] Major Architectural Problem with Evolution

I have found what appears to me to be a majot architectural flaw within
evolution. It seems that somewhere there is a config file that evo opens at
the time it gets executed. This file apparently stays open all during the
evo session. This is well and good and cool until you run out of filesystem
space...... When the evolution session ends it apparently writes whatever is
necessary to this file, closes it and the world is good, unless you have no
filesystem space. In this scenario the file doesn't get written and all data
that was be saved can not be.

End result is that when you clean up the filesystem problem and try to
restart evolution it doesn't see this prerequisite config file with any
content and makes the assumption you are a new user and need to configure a
new session. I have seen the problem with kmail before.... The more
appropriate design would be to read the config data from the file(s) at run
time, but not open the file for appending or writing. If you make changes to
the environment that need to be saved, this can occur as you shutdown. If
you have no filesystem space and the data can not be written, you lose a
little work, but your work environment remains intact.

Has this issue been dealt with before?  If so, how I can I recovery my
identity as an evo user without completely destroying my environment. I need
so serious help help. I like evo, but I'm going to be really sad and angry
if I need to re-do this environment again.

What is the most appropriate method for backing up an evolution
configuration for maximum recoverability? Any suggestions, hints, or
condolences would be greatly appreciated.

Sam Williams
sam williams hs utc com
samurai acm org

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]