Perhaps as part of installing gmond it could be recommended to go the extra
step to set up rysnc+ssh to distribute gmond, using the ssh-keyinstall
script available on the net or preferably an improvement on this particular
script that would automate the setup of ssh keys even further. Then
replacing gmond's to a new version on even huge installations shouldn't be
too much effort. As part of the install a unique gmond user would be
suggested to be created to tie together all the machines.

Also how about breaking down gmond even further into a sub components that
allow for the streaming of files through it, to/from via multicast. Then
future versions and gexec modules etc could be streamed out, perhaps even
wrapped through ssh encryption.

----- Original Message -----

>
> > There is a fairly large user base of OSCAR installs using 2.2.3 so it is
not
> > trivial to go around to all of those and replace the version of ganglia.
> >


Reply via email to