Slow expireover

Russ Allbery rra at stanford.edu
Tue May 18 12:26:38 UTC 2004


Mike Zanker <mike-sender-6677e0 at zanker.org> writes:
> On 17 May 2004 02:09 -0700 Russ Allbery <rra at stanford.edu> wrote:

>> You'll be able to tell right off if you look at top output while
>> expireover is running.  If you have no free physical memory and are
>> well into swap, that's probably the problem.

> OK, my MRTG graph indicates that free memory never dropped below around
> 45MB during last night's expireover, which took 2 hours and 11
> minutes. In fact, free memory went up to 134MB when expireover started
> and gradually fell to around 45MB over the time it ran.

Hm.  Really not sure what's taking so long, then.  It might be worthwhile
to run truss on expireover while it's running just to see what it's
spending its time doing.

-- 
Russ Allbery (rra at stanford.edu)             <http://www.eyrie.org/~eagle/>

    Please send questions to the list rather than mailing me directly.
     <http://www.eyrie.org/~eagle/faqs/questions.html> explains why.


More information about the inn-workers mailing list