Nagios for client management?

[Matthew Pounsett]

On 12-Nov-2008, at 14:09 , dale sykora wrote:

> Hello,
>  Nagios seems to be a good client monitor system.  I was wondering if
> anyone also uses it as a client management system?  By management,  I
> mean running update scripts and other software on various Linux
> clients.  For instance, I'd like to be able to tell clients to  
> update a
> perl module with cpan or yum update some_rpm_package or download,  
> untar,
> compile, install some in house software.

You could probably wedge something like that into Nagios, but there is  
software out there better suited to the task: configuration management  
and change management software (particularly the former).  See  
cfengine, bcfg2, puppet, to name only three.   I was also recently  
referred to an interesting paper which makes references to using  
configuration management software to manage other (client)  
organizations' systems, here <ftp://ftp.mcs.anl.gov/pub/bcfg/papers/directing-change-with-bcfg2.pdf 
 >.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 194 bytes
Desc: This is a digitally signed message part
URL: <https://www.monitoring-lists.org/archive/users/attachments/20081112/3bad9595/attachment.sig>
-------------- next part --------------
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
-------------- next part --------------
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null