Re: Gborg: announcement by 404

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160


>> I'll reiterate my offer to write a web-log scraping script for the main site
>> and extend it to pgfoundry, to at least start triaging some of the worst
>> effects of the move if nobody has other ideas.

> Which web-log do you need?

On whichever box pgfoundry is on, assuming all gborg URLs are redirected there, 
read access to the apache error logs. I'm not sure where pgfoundry logs its 
"project not found" requests, but access to that as well. If it isn't logging 
those, we'll have to hack that in. :)

As for the main site, just tell me where the logs are - I've got an account 
there, but the only error_log files I've found are empty.

Thanks much,
- --
Greg Sabino Mullane greg@turnstep.com
PGP Key: 0x14964AC8 200711132350
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iD8DBQFHOn6vvJuQZxSWSsgRA1ZTAKDl5tG+Aevi8rQccq/wan5fg+V07QCgpIB3
DjNWAQvydD98H3B9Wrk3iRk=
=IX7S
-----END PGP SIGNATURE-----