[Orca-users] procallator, the memory hog

OG ogjunk-orca at yahoo.com
Fri May 12 10:43:26 PDT 2006

Just in case anyone is interested.

Two days ago:
  57648  53m  648 S  0.0  1.3  48:04.29 initlog -q -c /usr/local/bin/procallator.pl

  71448  67m  648 S  0.0  1.7  61:38.64 initlog -q -c /usr/local/bin/procallator.pl

But this doesn't look like procallator.pl.
It looks like the memory hog here is this thing called 'initlog'.

Am I the only one with this problem?  This is running on a Fedora Core 3 system.


----- Original Message ----
From: OG <ogjunk-orca at yahoo.com>
To: orca-users at orcaware.com
Sent: Wednesday, May 10, 2006 1:08:06 AM
Subject: [Orca-users] procallator, the memory hog


I'll be trying the latest Orca snapshot shortly, but am wondering if Procallator has a known memory leak issue?
I'm asking because I've been running procallator from 0.27 version for about 7-10 days, and it went from using only a few MB or RAM to using over 50MB of RAM.
For example:
  57648  53m  648 S  0.0  1.3  48:04.29 initlog -q -c /usr/local/bin/procallator.pl

The first two numbers are memory (VIRT and RES from top).

Is this a known issue?
If this is not the appropriate place to deal with procallator, please let me know.


Orca-users mailing list
Orca-users at orcaware.com

More information about the Orca-users mailing list