> So, you use the Solaris box to generate the graphs and the RHEL boxes > to collect stats? I am not sure how silly this idea is, but couldn't > you use RRDCACHED to create a distributed model with the RHEL sending > updates to the Solaris box so only the Solaris box deals with RRD > files?
I agree that the RRDCACHED solution might be best for you, since the clients then do not need to be the same architecture as the server. HOWEVER, you would most likely need to compile the trunk version of rrdtool, else rrdcached support will be for updates only, not for creates or other features. The rrdcached in the 1.4.x branch is limited to just update, fetch and graph IIRC. We use rrdcached here, with one central RRD server handling the rrdcached and the web frontend, then several MRTG servers collecting data and sending via rrdcached. It makes for better performance, and no bother about NFS or similar (which hoses performance). RRDCACHED is easy to use as you can just set the RRDCACHED_ADDRESS environment variable and existing software should work (provided you don’t use updatev... or other functions not supported via rrdcached in the version you're using) Steve Steve Shipway ITS Unix Services Design Lead University of Auckland, New Zealand Floor 1, 58 Symonds Street, Auckland Phone: +64 (0)9 3737599 ext 86487 DDI: +64 (0)9 924 6487 Mobile: +64 (0)21 753 189 Email: s.ship...@auckland.ac.nz Please consider the environment before printing this e-mail
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ rrd-users mailing list rrd-users@lists.oetiker.ch https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users
