[PATCH 07/17] Rework lock/pidfile. Make ui class var of OfflineImap

Sebastian Spaeth Sebastian at SSpaeth.de
Thu Dec 2 10:50:28 GMT 2010

On Wed, 01 Dec 2010 23:47:22 -0600, Rob Browning wrote:
> Sebastian Spaeth <Sebastian at SSpaeth.de> writes:
> > The old offlineimap never ever  deleted the lock file, so our new offlineimap fails thinking it is still being locked. Use a different lock file location. NEVER RUN the old and the new offlineimap at the same time now.
> Perhaps I misunderstand, but wouldn't it be safer to continue using the
> same lock file, and just print a warning (explaining how to fix the
> problem) and exit if the lock file exists? i.e.:
>   $ offlineimape
>   ERROR: exiting because foo/lock exists.  If you are *certain* that
>   offlineimap is not running, please delete the file and try again.
> I'm just wary of the approach described above because it sounds like the
> failure case could be catastrophic with respect to the user's data.

As the new offlineimap would store its LocalStatus in an sqlite
database, and the old one in plain old textfiles, one can not go back
and forth between older (aka 0.6.2) and newer versions, there is no
forward-compatability in 0.6.2.

Using the same lockfile name would have no different effect but that the
user has to delete the existing one manually the first time he runs a
newer offlineimap.

not sure what the best strategy is...

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/offlineimap-project/attachments/20101202/5a7c1dc9/attachment-0001.sig>

More information about the OfflineIMAP-project mailing list