We've been thinking about almost the same functionality for managing
monit upgrades from m/monit.
M/Monit can have repository of various monit binaries (various
versions and platforms) and it could be easily to centrally manage
monit agents from M/Monit this way (upgrade monit with one click).
There is also security aspect of the possibility to replace the binary
on server (whether monit or different application) has to be
super-safe otherwise it could be security risk. It should be possible
to disable it at compile time and it should be disabled by default
plus good documentation and explanation of security related issues
needs to be added.
If you want to work on this functionality for monit, it could be
interesting :)
Thanks :)
Martin
rory wrote:
I'm implementing a feature locally, and was wondering what the
reaction would be for me to implement it in the main source.
I'm planning on using m|monit and monit as a service console for our
production service. Besides just stop/start/monitor, I also want to
use it to trigger updates of the running service. To do so, I plan on
adding an action to monit that would let me execute a script. Note
that this is not the same as execute script on alert, this is on the
same level as start/stop/etc.
So, is anyone in favor of me putting it into the main source, or
should I just maintain it separately?
_______________________________________________
monit-dev mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/monit-dev
_______________________________________________
monit-dev mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/monit-dev