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

[Yves <yme...@pe...>]

> Yves,
>
> I kept the original thread in the 'users' mailing list, my thinking
> being that they are the ones who uss this, and will therefore know.  I
> hope we get some response from them about who still uses this.

We should talk here on perfparse-devel-int and post our conclusion on per=
fparse-users
and ask for their opinion. If we flood perfparse-users with that thread, =
nobody will
read our last mail with the conclusion, and nobody will say who still use=
s it.
This is why I moved to perfparse-devel-int.

> I my self use the perfparse.sh script on a live server.  I do a clean
> parse every hour, which is the way I want to run that server.  I have
> not upgraded this one for a while, so was unaware of the nagios.lock
> being taken out of the config.  Do you remember which version this was
> removed?

I remember now that there are 2 things.
- nagios reboot with perfparse : in 0.100.7 and removed in 0.101 ? Check =
the ChangeLog :)
- nagios reboot thanks to the script : new feature of the script since 0.=
101 ?

I forgot that feature of the script.
So yes, there is still a nagios lock. But it should be removed of the per=
fparse config.
This is the nagios config only, and a parameter of perfparse.sh script.

> Therefore I would prefer it is supported as-is.  It's a nice ability if
> people want it, although there may be better methods.

I think it's the best method.
Provide the tool, and administrators provide script for running the tool =
the way they
want. And we graciously give such a script :)

Do you want to support it ? if yes, I see no problem, but you should upgr=
ade that script
at every new version.
When you install a new perfparse version, you get a perfparse.sh.example =
script. So the
perfparse.sh script you have is still the old one, that continues to work=
 for you. Maybe
users have a different script. Be sure that you are running the latest on=
e :)

> I also comment on the 'contrib' directory.  This contains the
> create/drops scripts for the database.  Which I chose because that's
> where Nagios puts them, so users may find them more easily.  These are
> supported.  Maybe these need another directory?

I agree with you.
I suggest a new directory, where you put the db create/drop scripts, *and=
 perfparse.sh*
script.
In 0.104.5, "make install" installs perfparse.sh.example". I suggest that=
 newer versions
don't install it (like the db create/drop scripts).
Users can find it in the scripts/ directory and install it themselves. Fo=
r packaged
solutions, this is the job of packagers to do it, not to do it, or to pro=
vide their own
scripts in their packages.



> I agree that the perfparse_deamon.sh should go.

I agree with you.
Do you want that I do all of that and make a 0.104.5ym1 release or do you=
 prefer to do
it yourself ?

Yves
--=20
- Homepage    - http://ymettier.free.fr - http://www.logicacmg.com -
- GPG key     - http://ymettier.free.fr/gpg.txt                    -
- Maitretarot - http://www.nongnu.org/maitretarot/                 -
- Perfparse   - http://perfparse.sf.net/                           -