Bugzilla Bug 66980

This is an ebuild for Tobi Oetiker's smokeping rrd tool. Smokeping measures
latency, latency distribution, and packet loss in a network, presenting the
results in graphs embedded in a web page. 

I feel that it goes best in net-analyzer/smokeping.

I have also attached a small file, smokeping-1.31.gentoo.tar.gz, which contains
configuration files specific to gentoo. Effectively, it's just a few patches,
but since I don't know how to create patches I made it like this.

Created an attachment (id=41457) [details]
ebuild for smokeping-1.31

Created an attachment (id=41458) [details]
Gentoo-specific config files

Files that must be changed from the distribution versions in order for
smokeping to run right out of the box.

Created an attachment (id=41459) [details]
Initial ChangeLog

please do not attach tarballs.  Please attach the contents of the tarball as
plaintext files.

Created an attachment (id=41486) [details]
Smokeping cgi script modified for gentoo

Created an attachment (id=41487) [details]
Smokeping config file modified for gentoo

Created an attachment (id=41488) [details]
smokeping perl script modified for gentoo

No prob, les voila. In any case, the tarball was just there because I was
hoping to get it into a mirror since my server isn't reliable. (If you've got
the time, I'm curios why tarballs aren't accepted.)

Its much easier to modify/read/manage from a bug monitoring point of view. If
you have to change just one file, you don't have to repackage the tarball
again, etc etc. Just many reasons. Thanks for the ebuild tho! I'm busies than I
can be right now, so I can't unfortunately look at it right now. Just be
patient tho, we'll eventually get to it :)

Cheers!

(From update of attachment 41458 [details])
No need for the tarball

Hate to bug you, but will this be put into portage soon?

Created an attachment (id=47420) [details]
smokeping 1.34 patch, made w/o knowledge of bug 66980

I've been hacking on this ebuild off and on for about a year.  Pretty much the
same idea.

Created an attachment (id=48266) [details]
smokeping version v1.34 and v1.36 into /usr/portage/net-analyzer

New version of smokeping.

NOTE!!!
I implemented alot of GLEP 11 in the two ebuilds in this patch.  I think you'll
find it quite easy to test out.

Here is how to experiment/test with this ebuild.

1)  Download the patch http://bugs.gentoo.org/attachment.cgi?id=48266&action=view into /usr/portage/net-analyzer.  (check for more recent if I find bugs)

2)  patch -p1 <smokeping_1.36.patch

3)  emerge smokeping

4)  config smokeping by editing /etc/smokeping

5)  /etc/init.d/smokeping start

6)  browse to http://localhost/cgi-perl/smokeping.cgi

7)  /etc/init.d/smokeping stop

8)  emerge --unmerge smokeping

9)  emerge sync - that will clean out the patch from your /usr/portage

please post feedback.

I'm trying out the ebuild mentioned above.  Smokeping will run for a couple
minutes, then die with no error logged.  Is this expected? Do I need to run it
via a cron job or is it supposed to continue running as a daemon?

I've isolated the problem with smokeping dying.  It hapens when smokeping
attempts to send a notification email.  The error I'm getting in the log is
this:

Can't call method "mail" on an undefined value at
/usr/lib/perl5/vendor_perl/5.8.5/Smokeping.pm line 144.

In sub sendmail ($$$)
        my $smtp = Net::SMTP->new($cfg->{General}{mailhost});
        $smtp->mail($from);  <---- dies here because $smtp is not defined.

Two more things:
1. There is a new version out, 1.37
2. Should the configuration files be put in a subdirectory of /etc/, like
/etc/smokeping/

Looks like I missed a dependency on "dev-perl/libnet" in my ebuild.  I'll try
to post new patch file with that in there and the even newer v1.38 real soon. 
As for question #2, I'd have to defer to a gentoo developer to review the
layout.

Created an attachment (id=50564) [details]
smokeping v1.34, v1.36, and v1.38 into /usr/portage/net-analyzer

Updated testing instructions.

1)  cd /usr/portage/net-analyzer
    wget http://bugs.gentoo.org/attachment.cgi?id=50564&action=view
    mv attatchment* smokeping_1.38.patch

2)  patch -p1 <smokeping_1.38.patch

3)  emerge smokeping

4)  configure smokeping by editing /etc/smokeping

5)  /etc/init.d/smokeping start

6)  browse to http://localhost/cgi-perl/smokeping.cgi after restarting apache

7)  /etc/init.d/smokeping stop

8)  emerge --unmerge smokeping

9)  emerge sync - that will clean out the patch from your /usr/portage

please post feedback (thanks Shawn!).

 * Also edit /etc/conf.d/apache2 and add -D PERL to APACHE2_OPTS
chmod: invalid mode string: `smokeping:smokeping'

i guess that should be chown

Yes, chown.

Created an attachment (id=52823) [details]
ebuild using Apache Package Refresh guidelines

During the March 5th gentoo bugday, I was informed about the Apache Package
Refresh effort. 
http://dev.gentoo.org/~vericgar/doc/apache-package-refresh.html

This ebuild would be used in addition to the 1.34, 1.36, and 1.38 ebuilds which
are GLEP11-ish and contained in the prior patch file.  This depends on mod_perl
2.0.0_r4.

Created an attachment (id=52824) [details]
ebuild using Apache Package Refresh guidelines

fix type-o

The Apache Package Refresh version of the ebuild depends on bug 77551

any ebuilds for v2.x yet?

Created an attachment (id=75167) [details]
smokeping 2.0.5 ebuild

Ebuild for latest version of smokeping, v2.0.5.

Numerous little fixes.

Added dump/restore functions to the init.d script, very handy.

Please remove the dependency on bug 77551.  Now that the mod_perl v2.0.1 ebuild
is checked into cvs, you can get smokeping running.  You will need to put
mod_perl into /etc/portage/package.keywords however.

# ebuild smokeping-2.0.5.ebuild install
>>> md5 files   ;-) smokeping-2.0.5.ebuild
>>> md5 files   ;-) files/smokeping
>>> md5 files   ;-) files/config.dist
>>> md5 files   ;-) files/78_smokeping.conf
>>> md5 files   ;-) files/digest-smokeping-2.0.5
>>> md5 src_uri ;-) smokeping-2.0.5.tar.gz
>>> Checking smokeping-2.0.5.tar.gz's mtime...
>>> WORKDIR is up-to-date, keeping...
>>> It appears that smokeping is already compiled; skipping.
>>> (clean to force compilation)
>>> It appears that smokeping has already been tested; skipping.

>>> Install smokeping-2.0.5 into /var/tmp/portage/smokeping-2.0.5/image/ category net-analyzer
chown: `smokeping:smokeping': invalid user  <<<<<<<<<<<<<<<<<<<<<<< HERE !!!!
man:
prepallstrip:
strip: i686-pc-linux-gnu-strip --strip-unneeded
strip: i686-pc-linux-gnu-strip --strip-unneeded
>>> Completed installing smokeping-2.0.5 into /var/tmp/portage/smokeping-2.0.5/image/

>>> Merging net-analyzer/smokeping-2.0.5 to /
 * Adding group 'smokeping' to your system ...
 *  - Groupid: next available
 * Adding user 'smokeping' to your system ...
 *  - Userid: 105
 * Do not specify /bin/false yourself, use -1

A few pointers, regarding smokeping-2.0.5:

- Unpacking tarballs is quite a pain.
http://dev.gentoo.org/~ciaranm/docs/mw-faq/attachments.txt
- The header is generally three lines long. We have longdescription in
metadata.xml and ChangeLog for additional information.
http://dev.gentoo.org/~ciaranm/docs/mw-faq/header.txt
- You should use pkg_setup() where you used pkg_preinst(). pkg_preinst() is ran
after src_install(). man 5 ebuild for details.
- There is no need to declare src_unpack().
http://dev.gentoo.org/~ciaranm/docs/mw-faq/redundant.txt
- -1 is used instead of /bin/false to maintain compatibility with OSs like
Gentoo/FBSD

Created an attachment (id=77014) [details]
smokeping 2.0.5 ebuild with edits

Apologies about the tarball.

Here are the edits.  Looks like the einfo call in portage 2.1 skips leading
blanks which hoses the ascii art...

(From update of attachment 77014 [details])
change mime type

(In reply to comment #16)
> 2. Should the configuration files be put in a subdirectory of /etc/, like
> /etc/smokeping/

Generally we defer to upstream defaults for whether it's directly in /etc. If
there is effectively no default and there are multiple config files, use a
subdirectory. If it's just /etc/smokeping.conf, e.g., put it straight in /etc.


On other notes, I'm a bit curious how those fowners and fperms calls work with
webapp-config. I'd think stuff like webapp_serverowned should be involved
somewhere. Also keywords should be set to ~arch for any tested architectures,
so somebody doesn't accidentally add it to the tree straight in stable. =)

Created an attachment (id=80042) [details]
v2.0.7 of smokeping plus bug fixed perl-core/libnet

Updated and tested smokeping-2.0.7 also fixed libnet it moved..

Smokeping 2.0.8 is out.

(In reply to comment #35)
> Smokeping 2.0.8 is out.
> 

2.0.9 is out now.

smokeping-2.0.9.tar.gz        14-Jul-2006 13:19  385K

net-analyzer/smokeping-2.0.9 is in CVS now, please sync in an hour or two to
get it, enjoy!
Best regards, CHTEKK.