> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:nagios-users- > [EMAIL PROTECTED] On Behalf Of Cormac O' Cianain > Sent: Wednesday, May 03, 2006 10:32 AM > To: [email protected] > Subject: [Nagios-users] status.sav to rentention.dat > > Hi there, > > Has anyone had to convert status.sav (Netsaint) to > retention.dat(Nagios) ? > I have just installed Nagios 2.2 and converted the log > and config files over but I haven't been able to find > an easy way to convert status.sav to retention.dat > (These are in very different formats). > > This needs to be done as I have 4 years of historical > data that I'd like to keep. I'm sure it can be done > manually but it could take a while. Does anyone know > of a easier way to do this?
There's really no need from my experience. status.sav and retention.dat just contain current status information and they'll be re-populated on the first check of each service based on your current configs and check results. status.sav is used by the CGI's to display current status and retention.dat is used by nagios to reload current state on restart. All historical information is in nagios/netsaint.log and the archives. The only thing that I can think of that might be interesting to port over from retention.dat might be acknowledgement status. I handled that by looking at the comments file for ACKNOWLEDGMENT and greping out the appropriate parts of the line to submit an acknowledgement external command. -- Marc ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642 _______________________________________________ Nagios-users mailing list [email protected] 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
