Re: [Perfparse-devel-int] perfparse.sh and perfparse_daemon.sh : obsolete, unsupported or live ?

[Ben C. <bcl...@pe...>]

Yves,

I can read the nagios.cfg file to obtain the location of nagios.pid.  I 
have a problem that none of the config variables tell me where this file 
is.  I cannot assume that PP is installed into the Nagios directory 
structure.

I think this was why this was written into the perfparse.cfg.

The reason I didn't notice the demise of this method was that my 
perfparse.cfg is old, I have not copied over the example for quite some 
time.  I thank the new user for finding this.

Personally I would suggest just adding this option into perfparse.cfg 
and an entry into config_file.c to match this so that every option is 
accounted for.

I will create the new scripts directory with the database creation 
scripts as well as perfparse.sh.  I'll edit the documentation where I 
can find it.  I hope I do not miss any!

Ben


Yves wrote:

>>Just another comment:
>>
>>Reinstating the perfparse.sh does not need any c code.   This reads the
>>perfparse.cfg file directly.  All that is needed is the nagios.lock
>>definition returned to this file :)
> 
> 
> A suggestion : don't mix the config of perfparse and the config of nagios :)
> 
> An admin would write a script to find nagios.lock directly in nagios config files, have
> a env variable or another mechanism, but not put that in perfparse.cfg.
> 
> As an admin, I even think that is it not the job of perfparse developers to provide
> those scripts, but the job of packagers and companies that sell support. But well, we
> have it and users enjoy it, so keep it in perfparse :)
> 
> Yves
> 


-- 
Ben Clewett  bcl...@pe...
PerfParse    http://www.perfparse.org
PP FAQ       http://wiki.perfparse.org/tiki-list_faqs.php