[Orca-users] Re: Procallator question

[Blair Zajac]

I can't look at 1 for a while, but here is the configuration file he
sent on September 26, 2001 (PST).  I changed the name of the file to
procollator just to distinguish it from orcallator.cfg.

There's some work that needs to be done on this file, as the URLs are
out of date, etc.

Best,
Blair

richmond at wildfire.com wrote:
> 
> I recently downloaded procallator to use with
> orca on a Red Hat 7.1 system.  I have things up and
> running but have 2 questions:
> 
> 1) For some reason, the procallator.pl script
>    (which collects the data on the machine)
>    writes the data file to the
>      /var/opt/orca/procallator
>    directory as well as the
>      /var/opt/orca/procallator/hostname
>    directory.  It either does this all the
>    time or every once and a while.  I've looked
>    at the script and it is not immediately obvious
>    to me why it does this.
> 
> 2) I noticed in the orca-users archive that Christian
>    Pearce sent his combined orcallator/procallator
>    configuration file to the group.  I tried to download it,
>    but I keep getting an error that the file cannot be found.
>    Does this configuration file exist somewhere else?  I'd like
>    to get a copy if I could.
> 
> Thanks,
> 
> Chris
> 
> --- In orca-users at y..., "Christian Pearce" <pearcec at c...> wrote:
> > For the record.  I have both procallator and orcallator *col files
> processed
> > with the same configuration for orca.  It wasn't difficult, but it
> wasn't
> > clear to me when I first started.  I just wanted to archive my
> results for
> > others.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: procallator.cfg.txt
Type: application/x-ns-proxy-autoconfig
Size: 31906 bytes
Desc: not available
URL: </pipermail/orca-users/attachments/20011012/1655dc0b/attachment.pac>