Ryan, Kill spike isn't very good. I've noticed that the timestamp isn't always the same on different systems. It is very likely that killspike is looking for the data on column 6, but that the timestamp might add two more columns. You then need to rewrite killspike and modify the lines which look for these values.
I have some documents on the subject laying at work. Will mail you from there. Peter > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Ryan Crouch > Sent: Thursday, February 14, 2002 12:10 AM > To: '[email protected]' > Subject: [rrd-users] Spikes Again > > > Hey all, > > I am trying to remove some spikes from some graphs that have failed today. > There is about half an hour of NaN records, which cause an 80mbit spike. > When I remove the NaN's nothing happens, and even if I remove the surround > ten lines, before and after, nothing happens to improve the graph spikes. > > Killspike gives me .. > > perl killspike.pl > Found 2 datasources > Malformed input at killspike.pl line 73, <IN> line 44. > > > Thanks in advance. > > -Ryan > > > > -- > Unsubscribe mailto:[EMAIL PROTECTED] > Help mailto:[EMAIL PROTECTED] > Archive http://www.ee.ethz.ch/~slist/rrd-users > WebAdmin http://www.ee.ethz.ch/~slist/lsg2.cgi > -- Unsubscribe mailto:[EMAIL PROTECTED] Help mailto:[EMAIL PROTECTED] Archive http://www.ee.ethz.ch/~slist/rrd-users WebAdmin http://www.ee.ethz.ch/~slist/lsg2.cgi
