Trac is basically unusable at the moment again due to heavy search
engine traffic - I will adjust robots.txt to try to get rid of the
problem, but it will likely take a couple hours to take effect since
each crawler should only read robots.txt every so often.
Cheers,
Michael
--~--~-~--~-
On Apr 5, 3:40 am, Harald Schilly wrote:
> On Apr 5, 4:34 am, mabshoff wrote:
>
> > the main
> > problem seems to be that the timeline can now be accessed at any point
> > you want and each ticket has a link to jump to the the point of the
> > timeline when it was created. This is quite expens
On Apr 5, 4:34 am, mabshoff wrote:
> the main
> problem seems to be that the timeline can now be accessed at any point
> you want and each ticket has a link to jump to the the point of the
> timeline when it was created. This is quite expensive for the database
> to construct ...
sounds like tra
On Sat, Apr 4, 2009 at 7:21 PM, Carl Witty wrote:
>
> On Sat, Apr 4, 2009 at 6:53 PM, mabshoff wrote:
>>
>> Hello folks,
>>
>> for the last couple hours Sage's trac has been very slow or completely
>> unresponsive. This is caused by the MS as well as Yahoo search engines
>> hammering the website
On Apr 4, 7:21 pm, Carl Witty wrote:
> On Sat, Apr 4, 2009 at 6:53 PM, mabshoff wrote:
>
> > Hello folks,
>
> > for the last couple hours Sage's trac has been very slow or completely
> > unresponsive. This is caused by the MS as well as Yahoo search engines
> > hammering the website (as can be
On Sat, Apr 4, 2009 at 6:53 PM, mabshoff wrote:
>
> Hello folks,
>
> for the last couple hours Sage's trac has been very slow or completely
> unresponsive. This is caused by the MS as well as Yahoo search engines
> hammering the website (as can be seen by the proxy error log as well
> as trac's l
