reg | 18 Oct 2011 08:42

How to 'clean up' a EXMH database.


OK, something has happened to my EXMH.
Every time I delete a message, I get the little circular icon saying that 
something is
going on, and a list of files being deleted.  This never clears.

I seem to remember that their is some program to 'verify' a EXMH database, and
possibly apply the corrections needed.  Since my attempts at looking at file 
permissions
have not found anything, Im going to need the help of something like that.

Can someone tell me what the name of that thing is?
My assumption is that its sitting down in the EXMH library, but I have no idea 
what
its name is.
--

-- 
                                        Reg.Clemens
                                        reg <at> dwf.com
Tom Lane | 19 Oct 2011 00:09
Picon

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

reg <at> dwf.com writes:
> OK, something has happened to my EXMH.
> Every time I delete a message, I get the little circular icon saying that 
> something is
> going on, and a list of files being deleted.  This never clears.

There isn't much of a "database" in there.  I'd bet on something being
screwy in ~/Mail/.exmhcontext, or possibly in the relevant per-folder
.mh_sequences file.  I've more than once noticed problems from
per-folder state somehow getting into the global .exmhcontext file.
Anyway, they're just text files, eyeball them and remove anything that
seems bogus.

			regards, tom lane
Julian H. Stacey | 20 Oct 2011 19:47
Favicon

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

Tom Lane wrote:
> reg <at> dwf.com writes:
> > OK, something has happened to my EXMH.
> > Every time I delete a message, I get the little circular icon saying that 
> > something is
> > going on, and a list of files being deleted.  This never clears.
> 
> There isn't much of a "database" in there.  I'd bet on something being
> screwy in ~/Mail/.exmhcontext, or possibly in the relevant per-folder
> mh_sequences file.  I've more than once noticed problems from
> per-folder state somehow getting into the global .exmhcontext file.
> Anyway, they're just text files, eyeball them and remove anything that
> seems bogus.

Yes, occasionaly stuff gets screwed & its just a case of removing
a few dot files, eg

cd ~/mail ; find . -name \.\* | xargs echo Might need to rm some of these

Of course if you do remove a few, the state table memory fails, ie
it may forget which mails youve read & which are new, so the blue
colour on some new mails may dissapear (though will return on new
mails after).

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.

Cheers,
Julian
(Continue reading)

Valdis.Kletnieks | 20 Oct 2011 22:59
Picon
Favicon

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
Exmh-users <at> redhat.com
https://www.redhat.com/mailman/listinfo/exmh-users
Robert Waldner | 21 Oct 2011 10:53
Picon

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


On Thu, 20 Oct 2011 16:59:56 EDT, Valdis.Kletnieks <at> vt.edu writes:
>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.

I use procmail as a frontend for rcvstore for that very reason - well, 
 and it does do nice filtering, of course ;)

cheers,
&rw
--

-- 
-- Like the autumn leaves
-- wu-FTPD updates;
-- I seek warm safety.
--      - Anthony de Boer

_______________________________________________
Exmh-users mailing list
Exmh-users <at> redhat.com
https://www.redhat.com/mailman/listinfo/exmh-users

Gmane