X-Original-To: pgsql-www-postgresql.org@localhost.postgresql.org Received: from localhost (mx2.hub.org [200.46.204.254]) by postgresql.org (Postfix) with ESMTP id E7AF311F8B82; Sat, 22 Apr 2006 15:20:09 -0300 (ADT) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Score: -2.483 X-Spam-Level: X-Spam-Status: No, score=-2.483 required=5 tests=[AWL=0.116, BAYES_00=-2.599] Received: from postgresql.org ([200.46.204.71]) by localhost (mx2.hub.org [200.46.204.254]) (amavisd-new, port 10024) with ESMTP id N+k2+2eqJGx0; Sat, 22 Apr 2006 15:20:01 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- X-Greylist: from auto-whitelisted by SQLgrey- Received: from noel.decibel.org (noel.decibel.org [67.100.216.10]) by postgresql.org (Postfix) with ESMTP id B92F611F6A28; Sat, 22 Apr 2006 15:20:00 -0300 (ADT) Received: by noel.decibel.org (Postfix, from userid 1001) id 3DCFB56423; Sat, 22 Apr 2006 13:20:00 -0500 (CDT) Received: (hashcash-sendmail, from uid 1001); Sat, 22 Apr 2006 13:19:58 -0500 Date: Sat, 22 Apr 2006 13:19:58 -0500 From: "Jim C. Nasby" To: Dave Page Cc: "Joshua D. Drake" , Magnus Hagander , "Marc G. Fournier" , greg@turnstep.com, pgsql-www@postgresql.org Subject: Re: Gborg still down Message-ID: <20060422181958.GB96357@pervasive.com> References: <20060421224531.GV49405@pervasive.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 6.0-RELEASE-p4 amd64 X-Distributed: Join the Effort! http://www.distributed.net User-Agent: Mutt/1.5.11 X-Hashcash: 1:20:060422:dpage@vale-housing.co.uk::sQVD7gg4ejvayRcy:0000000000000 0000000000000000000000003U+h X-Hashcash: 1:20:060422:jd@commandprompt.com::M5LYiZ7nFEePg21c:00000000000000000 0000000000000000000000001io6 X-Hashcash: 1:20:060422:mha@sollentuna.net::+p+LQftBLItWhHKr:0000000000000000000 0000000000000000000000002iBp X-Hashcash: 1:20:060422:scrappy@postgresql.org::SNIzmrkTBKmrmWyt:000000000000000 0000000000000000000000001Nqe X-Hashcash: 1:20:060422:greg@turnstep.com::ygmfOHKma5Nd2XwW:00000000000000000000 0000000000000000000000008L/l X-Hashcash: 1:20:060422:pgsql-www@postgresql.org::a7rkiXVsudwLLNRu:0000000000000 0000000000000000000000006ED0 X-Archive-Number: 200604/160 X-Sequence-Number: 9936 On Sat, Apr 22, 2006 at 09:01:48AM +0100, Dave Page wrote: > As we already said, we do monitor them. However, we monitor that they are > running - ie. Do we get a response from Apache, ssh, rsyncd or whatever. > Checking whether the archives/search are serving up to date content would be > a whole other (difficult) problem altogether. ISTM it wouldn't be that difficult if whatever updated the archives stuffed the current time in a file somewhere once it was finished... BTW, lest it sound like I don't appreciate the work of everyone who keeps the various sites up, I do. But it hurts our credibility everytime someone can't get to one of our sites, or the archives are out of date, or search doesn't work, etc., etc. I know there's been some big improvements made recently; I'm just hoping that we can get monitoring setup for everything that's currently not being monitored. -- Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461