Quote:
Originally posted by Choker
Yep, but at the same time your total monitored time is reflected the same way. So 20 servers being monitored would show 20 hours total monitored time after one hour. But no matter what you are going to continue to cry like a baby aren't you?
|
Listen to you, at it again. These people are being polite, trying to explain some flaws in your script, and you're off being a cock about it.
If you're going to classify a period of time your master server is unable to hit the sites running your monitor script due to a 403 or 404 error (or any other error related to the webmaster fucking something up) as "Host downtime" you are misrepresenting the facts. If that's causing a host to lose business, you better believe you can get sued especially when most hosts can back up the fact that their server was up with MRTG graphs, server logs, server performance graphs, and dozens of other means.
Lose your fucking attitude and listen to what the people are saying, stop being so defensive and consider for a moment they're trying to offer their opinions to help make your "service" better. What use is it to anyone if it's not accurate? You seriously need to reconsider what is considered host downtime, or remove it all together. I know you thought it would be cool and everyone would worship you if you could show how shitty all the hosts are, but from what I (and many others it would seem) am seeing, it's not working.