Originally Posted by pinga123
have below queries regarding the environment.
1)Will it be a good idea to make a rpm out of those scripts and maintain a version control.
2)How do i avoid root usage ?
As the environment is build on xen virtual technology and most commands only run using root.
3)Is there any other way of doing it?
It is always a good idea to use version control. Where I work we keep all of our scripts and system configurations in subversion. I don't see a need to build rpms out of your scripts unless the have explicit dependencies you wish to reference for them and you're not planning to have them installed on all machines through cobbler. If all machines have the same scripts then just let cobbler handle it and there's no need to go out of your way to create rpms for a few simple scripts.
chrism01 is doing it the same way I would suggest. sudo is very useful for those situations and I've done that before without much effort.
Our DB admins monitor their Oracle databases using Oracle Enterprise monitor manager. They don't seem to ever catch anything with it though. I run checks on it using Icinga
and set up escalations so that it emails them when systems are warning or critical based on certain predefined conditions, which works well. Also we graph historical information on the system using munin
. I integrated munin into Icinga so that it is relatively easy to view long term statistics on a machine when viewing real time alerts. I wrote a plugin for monitoring database connections to Oracle and will alert when a certain threshold has been met.
Those aren't the only monitoring utilities but they're good quality.