Assaf Gordon wrote: > I followed with 'bzr'. Excellent! Thanks Assaf!
> The checks are: > > bzr branch bzr://bzr.savannah.nongnu.org/gnewsense/docs > bzr branch bzr+ssh://[email protected]/gnewsense/docs > > rsync -avhP rsync://bzr.sv.gnu.org/bzr/gnewsense/docs > > wget -O/dev/null https://bzr.savannah.gnu.org/lh/gnewsense/ > wget -O/dev/null https://bzr.savannah.gnu.org/r/gnewsense/ > wget -O/dev/null http://bzr.savannah.gnu.org/lh/gnewsense/ > wget -O/dev/null http://bzr.savannah.gnu.org/r/gnewsense/ Add to this a check for the robots.txt file. I noticed that it was shadow'd for bzr and many robots were crawling. I unshadowed it and the robots should back down now. > For the 'svn' checks I'd add this (which works fine): > rsync -avhP rsync://svn.sv.gnu.org/svn/administration/ Good catch! I added it to the list. I also added the above to the bzr section too. :-) > A small question: > Since all the nginx virtual hosts use the same log file, > would it be useful to change to log format to have the server name as well ? That is a problematic question. Do you have any particular goal in mind with this question? Is there a particular reason you need this information? As far as I know there isn't any way to add the server name to the logs. $server_name isn't one of the log variables. The only way to do that is to split the logs into separate files. Which makes other things much more difficult. If it is at all practical to do it is much easier to deal with the combined file. I am running these two commands frequently to make observations: root@vcs0:~# multitail /var/log/nginx/{access,error}.log And for both nginx and apache together. Apache access is mostly duplicated but the error log is unique to each. root@vcs0:~# multitail /var/log/{apache2,nginx}/{access,error}.log Currently the error log is not quite zero errors. The goal is zero errors however. The crawlers are actually helping in this case because they are pointing to problems. Bob
