OK, ok... I put something together and sent it to you and Earl for review.
I'm not sure about the bounty though since I did say that I'd do this
before.
The patch is awesome and the bounty is yours. Very nice work.
-Jeff
Modifying code to remember last message number is
straight-forward and independent of any file system that
may be in use.
Ok, to spice things up I'm offering a $300 bounty for whoever writes
the patch that gets accepted into the MhonArc codebase.
Modifying code to remember last message number is
straight-forward and independent of any file system that
may be in use.
Ok, to spice things up I'm offering a $300 bounty for whoever writes
the patch that gets accepted into the MhonArc codebase.
OK, ok... I put something together and
How can I be most helpful?
-Jeff
Happy Easter and ping... :)
I can work on a patch in the next few days unless Earl tells me to
back off because he's going to do it. :)
I think an option for mhonarc to avoid the directory listing would be
quite helpful, at least in my situation.
I would love to have access to the last message number after a MHonArc
run.
I've been working on an SQL-based message store that is used entirely
for searching, displaying indexes,
On Mon, Apr 6, 2009 at 12:16 PM, Jym Dyer j...@econet.org wrote:
=v= I handle a similar situation like this: do a directory-wide
operation, then record the directory's modification date. Next
time around, check the directory's modification date and skip
the operation if it hasn't changed.
On April 1, 2009 at 21:00, Jeff Breidenbach wrote:
I *think* mhonarc is doing a listdir operation as
a safety check to avoid clobbering existing message files. (I tried to
find out via strace, but managed instead to confuse myself). Is this
actually true, and if so, can the directory listing
Great, that is a possible performance enhancement for the future, as
very large directories can be slow to read, even when totally cached
by Linux. For the immediate term, I'll talk with the aufs folks to see
if directory reads can get faster.
$ time ls -U /dev/null # cached
real0m1.471s
This question is a little esoteric.
I decided to try improving mhonarc's archiving speed with one of those
whiz-bang solid state drives from Intel. Unfortunately, they are
pretty low capacity and I can't fit all the data. So I decided to go
with a hybrid strategy; all new writes go to the SSD,
10 matches
Mail list logo
