> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:nagios-users- > [EMAIL PROTECTED] On Behalf Of Miles O'Neal > Sent: Tuesday, July 18, 2006 11:18 AM > To: nagios-users@lists.sourceforge.net > Subject: [Nagios-users] config files and upograding > > We've been running 1.2 pretty much since it came out. > I'd liike to try a 2.x version, but nowhere am I > finding anything about config file changes. Can I
http://nagios.sourceforge.net/docs/2_0/whatsnew.html > just start with the 1.2 config files and have it work? With only minor modifications. Some macro names have changed and moving contact_group definitions from the hostgroup{} to the host{} definitions was pretty much all I needed to do here but I have a pretty simple config. > If not, can someone point me to a doc about the steps > to upgrade? > > The upgrade from whatever nagios was before to nagios > was a major pain. (In fact, I wish there had been an > option for using the old format; I prefer to manage config > files with old-fashioned *nix command line tools, and > that works much better when each line is an entire config > command!) Nagios 1.x does support the old Netsaint single-line definitions (http://nagios.sourceforge.net/docs/1_0/xoddefault.html). They were specifically maintained for backward compatibility, you just needed to specify that at compile time. 2.0 doesn't in favor of the more flexible template definitions. -- Marc ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ 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