Peer1 has helped me to shutdown the dsmc service properly. It can be
controlled with the service command (start/stop on dsmc and dsmcat). I
have updated the wiki info on SAC:Backups accordingly.
Also, I have added /project/query to the Trac robots.txt. From what I see
as long running trac requests, I'm concerned that robots are issuing some
expensive Trac queries that are slowing things down. Robots may now have
trouble finding all the tickets for index.
Hopefully we will see some easing of problems from one or both of these
changes.
Best regards,
--
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up | Frank Warmerdam, warmerdam@pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush | Geospatial Programmer for Rent
On Wed, Nov 25, 2009 at 7:01 AM, Frank Warmerdam <warmerdam@pobox.com> wrote:
...
Also, I have added /project/query to the Trac robots.txt. From what I see
as long running trac requests, I'm concerned that robots are issuing some
expensive Trac queries that are slowing things down. Robots may now have
trouble finding all the tickets for index.
A solution might be to submit a sitemap (XML) to those search engines.
AFAIK, like this we should be able to control what's indexed and what's not.
On Wed, Nov 25, 2009 at 11:32:50AM +0100, Markus Neteler wrote:
On Wed, Nov 25, 2009 at 7:01 AM, Frank Warmerdam <warmerdam@pobox.com> wrote:
...
> Also, I have added /project/query to the Trac robots.txt. From what I see
> as long running trac requests, I'm concerned that robots are issuing some
> expensive Trac queries that are slowing things down. Robots may now have
> trouble finding all the tickets for index.
A solution might be to submit a sitemap (XML) to those search engines.
AFAIK, like this we should be able to control what's indexed and what's not.
Sitemaps don't generally say what not to index, only what to index.
The right way to say what not to index is via robots.txt.