Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am looking for a software to monitor any configuration changes in the data center for Linux, windows, or both. We have a mixture of windows 2003 and 2008 servers and redhat linux servers (primarily centos). I would prefer to have it server based with agents to install so I can monitor from a single machine but i'm open for suggestions. This is what I am looking for in the software and any ideas would be greatly appreciated.
1. install software on new and previously configured machines
2. set the "base" configuration
3. monitor the configurations for any changes
4. (optional) some sort of notification for any changes made to those "base" configurations (email would be cool but isn't necessary)
Don't have any software in mind that works for Windows, but I'd like to
suggest a different approach (for at least the Linux systems).
Rather than monitoring configuration on the servers have the config in
a centralised repo, and disallow/disable changes on the servers themselves.
At least that way you'll have time, date, person and actual change handy,
and do a targeted fix if a change breaks something. After all, the monitoring
may get broken/disabled if a change affects machine behaviour or networking,
and your agents don't do their job any more.
Just my 2cents ...
And for the approach I mentioned you could look at things like puppet ...
It certainly should, the problem is that you don't have an
easy interface to push the changes - with a bigger number of
machines this would become quite manually involved ... puppet
can be made to use svn for it's config store.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.