how to update from 1.1 to 1.2

[Ron Huff]

I recently updated 1.1 to 1.2; this is as easy as it gets.  Just protect 
any source
you've modified.  Of course you protect your config files with your life,
however these are not threatened and are completely transferable to 1.2.

I'm not sure how much control you have with rpms; I use tarballs.  Just
take the new source tree thru the 'make install' step,  and you're ready
to go ( I use the INSTALLING guide )...config files should remain untouched
and all worked as before for me.
- Ron Huff



markus auchmann wrote:

>hi guys
>
>yes as you can see my question is how to update from 1.1 to 1.2, i used the 1.1 rpm's so whats easier, uninstall the 1.1 rpm's and install the 1.2 rpm's or is it easier to just overwrite some 1.1 files to get 1.2 working (and if it is so, wich files should i replace)
>
>thanks in advance,
>
>markus auchmann
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by Sleepycat Software
>Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver
>higher performing products faster, at low TCO.
>http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
>_______________________________________________
>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
>
>  
>



-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver
higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
_______________________________________________
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