I'm going to guess no as there are configuration changes between 1.x and 2.x.
I seem to recall a script somewhere that would try to take your 1.x config and make it 2.x compatible but I honestly don't remember where I saw it or if it was just talk about making one. --Dennis > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf > Of Network Administrator > Sent: Wednesday, February 15, 2006 1:50 PM > To: Nagios Users Mailinglist > Subject: [Nagios-users] Nagios 2.0 RPM > > I noticed that 2.0 stable is out. Is it safe to do a "rpm > -Uvh nagios-2.....rpm" to upgrade the v1.3 installation? If > not, what would be the recommended way to upgrade the installation? > > Thanks. > > Irwin Dulan II > Network Administrator > Fuller Theological Seminary > > > > ------------------------------------------------------- > 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://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&; > dat=121642 > _______________________________________________ > 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 > ------------------------------------------------------- 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://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 _______________________________________________ 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
