From: Ben C. <Ben...@ro...> - 2005-01-07 14:01:37
|
Sorry gues, let me catch up with my email: Tim, how do you feel about adding your scripts to the installation? If so you have a choice of 'contrib' where unsupported additions are kept, and 'scripts' where supported additions are kept. The choice is yours :) Other files: <file> contrib/check_perfparse.sh </file> I'll credit this to Yves. But I would like to rename it 'check_perfparse_dropfile.sh'. Since this is what is does. <file> contrib/perfparse_deamon.sh </file> Will be deleted. <file> config/perfparse_nagios_command.pl </file> <file> config/perfparse_nagios_pipe_command.pl </file> Yves, should we use the version which Tim has enhanced? These are currently in the 'config' directory. Should these be moved to 'scripts'? Lastly I will write a minimum program for returning whether the database version is correct or not. Which will be in nagios_plugin protocol. I'll doc this when complete. Regards, Ben. Tim Wuyts wrote: > All, > > I wrote two scripts, and posted them on the wiki: > http://wiki.perfparse.org/tiki-index.php?page=CheckingPerfparseWithNagios > > I called them: > check_perfparse.pl and check_perfparse.sh > > The first is a nagios plugin, the second should be used as an event > handler whenever the plugin reports an error. check_perfparse.sh is > based on restart_httpd.sh. > > The check_perfparse.sh script in the contrib directory is something > completely different, and was not written by me. I propose to change > the name of my check_perfparse.sh into > nagios_eventhandler_restart_perfparse.sh (I'll update the wiki > accordingly), unless someone comes up with a better name. > > As for the two .pl scripts in the config directory: > I have nothing to do with the original perfparse_nagios_command.pl and > perfparse_nagios_command_pipe.pl. I do use a slightly modified version > of the _pipe script (see below, I simply added a line to check if the > file exists AND is a pipe). > > Tim > > <FILE name="perfparse_nagios_pipe_command.pl"> > #! /usr/bin/perl -w > use strict; > my $file = shift @ARGV; > exit(0) unless (-p $file); > open FH, ">$file" or die "'$file' could not be opened for appending\n"; > print FH join("\t", @ARGV); > print FH "\n"; > close FH; > </FILE> > > On Fri, 7 Jan 2005 11:40:52 +0100 (CET), Yves <yme...@pe...> wrote: > >>>I have cc'd this to developers list in case any other contributer knows >>>of or wants to add a script to PP. >>> >>>May I check the scripts to ensure the correct author credited? >>> >>>check_perfparse.sh - Tim >>>perfparse_nagios_command.pl - Tim ? >>>perfparse_nagios_pipe_command.pl - Tim ? >> >>I wrote those 2, but they were copy/pasted from a mail. Was that Tim ? I don't remember. >>If you find the reference of that mail, I don't mind to credit only the one who sent >>that mail. Otherwise: >>Credits : Yves thanks to somebody who sent the main lines by email. >> >> >>>perfparse_daemon.sh - Yves >> >>Yes, but that one should be removed :) >> >> >>>perfparse.sh - Ben / Yves >> >>OK >> >>Ben, wait for my patch about that bug in the history command I told you about. >>However, if you cannot not wait more to release 0.104.7, do it : nobody uses the feature >>with the bug yet :) >> >>-- >>- 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/ - >> >> > > > > ------------------------------------------------------- > The SF.Net email is sponsored by: Beat the post-holiday blues > Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. > It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt > _______________________________________________ > Perfparse-devel-int mailing list > Per...@li... > https://lists.sourceforge.net/lists/listinfo/perfparse-devel-int > |