Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 2BDF82E0056 for ; Tue, 25 Mar 2008 22:54:38 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 91304-02 for ; Tue, 25 Mar 2008 22:54:34 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from vms173001pub.verizon.net (vms173001pub.verizon.net [206.46.173.1]) by postgresql.org (Postfix) with ESMTP id 9F4DB2E0051 for ; Tue, 25 Mar 2008 22:54:34 -0300 (ADT) Received: from new-host.home ([71.245.161.199]) by vms173001.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0JYB001SWEMNYLV1@vms173001.mailsrvcs.net> for pgsql-www@postgresql.org; Tue, 25 Mar 2008 20:54:23 -0500 (CDT) Date: Tue, 25 Mar 2008 21:54:22 -0400 From: Robert Treat Subject: Re: New email list for emergency communications In-reply-to: <20080325184421.73d2f869@iridium.wars-nicht.de> To: pgsql-www@postgresql.org Cc: Andreas 'ads' Scherbaum Message-id: <200803252154.22537.xzilla@users.sourceforge.net> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7bit Content-disposition: inline References: <20080325184421.73d2f869@iridium.wars-nicht.de> User-Agent: KMail/1.9.1 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200803/587 X-Sequence-Number: 14706 On Tuesday 25 March 2008 13:44, Andreas 'ads' Scherbaum wrote: > On Mon, 24 Mar 2008 23:51:19 -0300 Marc G. Fournier wrote: > > - --On Monday, March 24, 2008 15:04:39 -0400 Bruce Momjian > > > > > > wrote: > > > When email was down this past week, I had no idea if the problem was > > > known and who was working on it. > > > > Trust in the fact that by the time you would notice a problem, we're > > already working on fixing it ... Stefan has everything monitored > > automatically, which sends out auto-notices to 'those that can fix it' > > ... by the time you would notice it, we're already deep into fixing it > > ... > > So i think the problem is not that you (sysadmin team) already know. > The problem is that the others does not know that you know. > > Try to communicate that you are working on a specific problem. One > possible solution: a status page, was already mentioned earlier. > > I have a couple of thoughts wrt this. AUIU we're using nagios, it should be possible to set up sysadmins and bruce with nagios accounts so we can login and view the pretty colors that explain what is up or down. Second, as I think about it, I think the only member of our sysadmin team who has ops on IRC is Joshua. Perhaps we should see about having a number of us get ops so we can post notices there. It won't reach everyone, but would hit a large % of people, and the network is completly seperate in all ways from the postgresql.org infrastructure. -- Robert Treat Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL