This is what I tried to explain. My original question actually was if it was just stupid luck that my hload got the the latest values from duplicate entries.
I was writing the updated values to the file, by appeding to it and therefore adding duplicate entries. By using a timer each 5 minutes the hsave option was called to prevent the file from exsesive (sorry for my bad english I mean very big) growth.
Actually your filter command in combination finding the actual bug (I did save multiple hashtables every 3 secs entirely) solved my problem.
