-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
> Done. Will be up on next sync as usual.
Thank you.
>> * Can we parse the web server error logs to proactively find
>> problems like this and get them fixed quickly?
> That's probably a good idea as well, though I haven't done it yet :)
> Know any ready-made tools that does that, or do we break out the good
> ole perl interpreter?
Both? :) I've got some scripts I've written that should do the job with
minimal modification. Point me at the logs, and I'll whip something up
to email you, me, and anyone else who wants in (worthy of a mailing list?)
- --
Greg Sabino Mullane greg@turnstep.com
PGP Key: 0x14964AC8 200711031424
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----
iD8DBQFHLLz/vJuQZxSWSsgRA7lkAJwLeqR69ptf9l2tDAi2OBRBciYT7ACglJvb
wqX8rieUZKfwBnJTo2fsVzk=
=bjtS
-----END PGP SIGNATURE-----