Re: How to 'clean up' a EXMH database.

On Thu, 20 Oct 2011 19:47:01 +0200, "Julian H. Stacey" said:

> Exmh is `just' a graphic front end to a number of back end CLI NMH
> commands, that may run asynchronously, & something may get inconsistent.
> Its not a single centralised monolithic application.

The single thing most likely to munch stuff (mostly sequences) is the fact that
the mh 'rcvstore' command doesn't do its own locking.  As a result, if you
manage to run 2 copies of 'rcvstore +foo' at the same time, there's a good
chance the 'unseen' sequence (and possibly the rest of .mh_sequences) will end
up with total zorkumblattum in it.

Even if nmh were to sprout proper locking, we'd need to do some corresponding
cleanups in the exmh code - there's several places it reads and parses things
like .mh_sequences directly rather than doing a `mhcommand`.

_______________________________________________
Exmh-users mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/exmh-users

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD8DBQFOoIvMcC3lWbTT17ARArSDAKDTK2yw82DHRR0Rxkx0Te2CS5E7pQCfU21H
qRQMF/V0lP6RsZREARRvA50=
=l4jK
-----END PGP SIGNATURE-----