[prev in list] [next in list] [prev in thread] [next in thread] 

List:       collectd
Subject:    Re: [collectd] how does collection.cgi work?
From:       "Hans-Cees Speel" <hanscees () hanscees ! com>
Date:       2005-10-31 21:13:51
Message-ID: 4366971F.16712.98B37D () localhost
[Download RAW message or body]



> Good morning :)
> 
> On Fri, Oct 28, 2005 at 08:00:30PM +0200, Hans-Cees Speel wrote:
> > I did not change the specfile, but the rpm's for sme (and thus rhe4)
> > are here:
> 
> Thanks a lot, I've linked them on the webpage.

Hi,
please relink to 
http://www.hanscees.com/sme7/collectdforsme7howto.html

Hans-Cees




> 
> > > As for the collection.cgi:
> > As much as I can understand that I still think it would be
> > supergreat if you could  just write like 5 lines in it explaining
> > where it does what. Especially what variables come from where. That
> > really makes the difference between something that works, and
> > something that is usefull in open source communities, still after
> > you stop maintaining it yourself.
> 
> Okay, you convinced me ;) I have to warn you though: The initial
> script was from a time when I thought every, uhm, `node' writes its
> own RRD files. That's why I split up the functionality into
> `collection.cgi' and `museum.cgi'. With the client/server
> possibilities all RRD files are within one directory which makes live
> easier.. So there will be big changes..
> 
> Also, I've linked your HowTo, thanks again for writing it :)
> 
> Regards,
> -octo
> -- 
> Florian octo Forster
> Hacker in training
> GnuPG: 0x91523C3D
> http://verplant.org/
> 

Hans-cees Speel @ http://www.hanscees.com
Trees @ http://www.bomengids.nl



[prev in list] [next in list] [prev in thread] [next in thread]