Tom Brown wrote: > >> >> This does make a good case for adding support for CentOS 4. I don't >> have any older CentOS, only RHEL so I wasn't aware that CentOS >> shipped with yum for this to be useful. >> >> Since you have made a good case, I have now updated the plugin to >> have compatibility for the older python 2.3, so pls try the latest >> version 0.6.6 and let me know how that goes for you on the old systems. >> >> http://www.nagiosexchange.org/cgi-bin/page.cgi?g=Detailed%2F2577.html;d=1 >> >> > > we use yum on RHEL 4 a lot so will be trying this out also > > thanks > Err, slight correction in my typing, I wasn't aware that CentOS *4* shipped with yum as RHEL 4 seems not to, I know my CentOS 5 does have it as does RHEL 5 (finally). I was under the impression that since CentOS is supposed to be purely a rebranded RHEL without the trademark logos etc, that it would follow RHEL closely, so if RHEL 4 didn't ship with yum, then neither would CentOS 4? I guess the CentOS guys realized how big a disadvantage this would be...
Did you add yum manually to RHEL 4 and if so, what implications are there for updates then, is there any official repo for that, or only 3rd party. If 3rd party, do they support security information support for yum? Otherwise you'd have to use --all-updates or --warn-on-any-update and keep the whole system up to date if you cannot differentiate between security and normal updates. -h -- Hari Sekhon ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Nagios-users mailing list Nagios-users@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
