Fix when not broken?

[Marc Powell]

> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
> admin at lists.sourceforge.net] On Behalf Of Edward Ford
> Sent: Wednesday, January 04, 2006 1:28 PM
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] Fix when not broken?
> 
> I have Nagios version 2.0b3 and it is running pretty good. Is there
any
> advantage to running/upgrading to version 2.0rc1? Do the upgrade
Nagios
> programs have anything different than the version I am using?

http://www.nagios.org/development/changelog.php

You'll always want to check this when upgrading as there may be
important information about manual changes you need to make. You should
be able to judge based on the changes made whether they're important to
you. You could always just do it to assist in the testing of course.

> Is the upgrade path:
> 
> 1)      kill Nagios and reinstall the new version?

Yup. Upgrades within the same major version are generally very painless.
You'll probably want to tar up your current nagios directory as a
fallback measure in the event of some critical problem but generally --

$ ./configure --with-your-options
$ make all
$ /etc/init.d/nagios stop
$ make install
$ /path/to/nagios -v /path/to/nagios.cfg
$ /etc/init.d/nagios start

> 2)      Upgrade program made to upgrade works well?

There isn't a dedicated 'upgrade program' that I've seen.

--
Marc


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
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