|
seems to me a very simple utility that would scan a "server-status" report for the word "unavailable" should ring a fucking bell.
maybe that's too easy, but it seems like that could nip problems in the bud very fast, and would be easy to implement.
or am i missing something here?
0.00 4.25 65.95.49.96 (unavailable) GET /30/small011.jpg HTTP/1.1
219-0 - 0/0/43 . 0.00 130 1 0.0 0.00 14.57 211.120.110.204 (unavailable) GET /takewalk/tn_DIV00012_MPG.jpg HTTP/1.1
220-0 - 0/0/46 . 0.00 130 2 0.0 0.00 3.58 211.120.110.204 (unavailable) GET /takewalk/tn_DIV00007_MPG.jpg HTTP/1.1
221-0 - 0/0/33 . 0.02 129 59922 0.0 0.00 5.40 68.11.210.226 (unavailable) GET /video/001_050/S037gaer44/CLIPS/MPEG1/CLIPS/15_VAR.MPG HTTP
222-0 - 0/0/55 . 0.02 129 68064 0.0 0.00 2.01 68.11.210.226 (unavailable) GET /video/001_050/S037gaer44/CLIPS/MPEG1/CLIPS/16_VAR.MPG HTTP
223-0 - 0/0/50 . 0.01 129 67181 0.0 0.00 2.35 68.11.210.226 (unavailable) GET /video/001_050/S037gaer44/CLIPS/MPEG1/CLIPS/17_VAR.MPG HTTP
224-0 - 0/0/30 . 0.02 129 65549 0.0 0.00 3.20 68.11.210.226 (unavailable) GET /video/001_050/S037gaer44/CLIPS/MPEG1/CLIPS/17_VAR.MPG HTTP
225-0 - 0/0/60 . 0.00 128 3 0.0 0.00 2.16 207.89.155.80 (unavailable) GET /1/index.html HTTP/1.1
226-0 - 0/0/57 . 0.02 128 1 0.0 0.00 2.37 68.75.177.124 (unavailable)
|