Now mhonarc.2.0.1 is able to generate multiple index pages. Nice !!!
I woud be very pleased to use this fonctionnality, but I also need
to use the REVERSE option and to run mhonarc on very large archive
(let's say 200 mailling list archives with some of them with
10.000 messages or more and about 20 new mails every day).
Using REVERSE is expensive since it causes all index pages
to be regenerated for each message addition.
From my understanding of mhonarc, if I run mhonarc for each new incomming
message with the -add option and <REVERSE> ressource, the process will
take more and more time because he will rebuilt all the messages.
No. It will only be forced to rebuild all the index pages. The
only message pages updated would be the ones for updating navigational
information (eg: next/prev messages of the new added message). In
general, only 1 or 2 message pages are updated for an added new message.
Is there a beter solution to use the nice job of mhonarc which compute
nicelly links between pages with low cpu ressources ?
You might consider not using REVERSE for mulipage archives.
Users can easily jump to the last page (if you use the $LASTPG$
variable) to get to the newest messages.
PS : how can I ask mhonarc to name generated files with ".shtml" suffix
insteed of "html".
This ability should become available in the next release.
--ewh
