760698253b
Earlier we would ignore *ALL* Exceptions that could occur during the fsyncing of our LocalStatus database. Ignoring all Exceptions is not the right thing here though. A recent commit improved the situation by raising at least KeyboardInterrupt Exceptions, but that is still not optimal. os.fsync() is available on Unix, and Windows starting in python 2.2.3. so it should always work. If it doesn't, something is wrong. It has been suggested to only catch EnvironmentError (ie SystemError and OSError) here, but even those should be thrown. Something *is* wrong if this fails and we should not ignore it. Signed-off-by: Sebastian Spaeth <Sebastian@SSpaeth.de> Signed-off-by: Nicolas Sebrecht <nicolas.s-dev@laposte.net> |
||
---|---|---|
.. | ||
folder | ||
repository | ||
ui | ||
__init__.py | ||
accounts.py | ||
CustomConfig.py | ||
imaplibutil.py | ||
imapserver.py | ||
imaputil.py | ||
init.py | ||
localeval.py | ||
mbnames.py | ||
syncmaster.py | ||
threadutil.py |