[Orca-users] Memory leak?

[David Michaels]

I can't speak to the memory leak itself (running Orca in verbose mode 
might give clues), but just so you know, you can combine all the 
different OS/platforms into one orcallator.cfg file, using the group {} 
stanza.

I have my IBMs, Windows, and Solaris boxes all computed by one instance 
of orca.  They all appear on the same web page, but separated into 
groups by OS.

It's mostly a matter of tuning the find_files string for each group so 
that it only picks up files for that group.

In my case:
group orcallator {
find_files              
/{obscured}/orcallator/(.*)/(?:(?:orcallator)|(?:percol))-\d{4}-\d{2}-\d{2}(
?:-\d{3,})(?:[^\.]*)?(?:\.(?:Z|gz|bz2))?
...
}

group winallator {
find_files              /{obscured}/winallator/(.*)/.*.tsv
...
}

# for my FlexLM log parsing stuff
group licencellator {
find_files              
/{obscured}/licencellator/(.*)/[^-]*-\d{4}-\d{2}-\d{2}(?:-\d{3,})(?:[^\.]*)?
(?:\.(?:Z|gz|bz2))?
....
}

And so on.

--Dragon

Borja Marcos wrote:
> Hi,
>
> I'm using Orca snapshot r535 on FreeBSD 7/amd64 (the 64 bit version).
>
> This machine uses Orca for some Solaris systems, FreeBSD (using  
> devilator) and some Linuces using procallator.
>
> And I've found that Orca is getting an outrageous amount of memory
>