s were affected, but I can tell you I really appreciate the
> way you look after us. You are the consummate pro.
** end quote [Jan Henkins]
Seconded. Mine was, but how you deal with a problem is a better recommendation
than never having a problem and not knowing. That sort of sounds backwards, but
it gives confidence that problems will be dealt with properly.
--
Paul Tansom | Aptanet Ltd. |
http://www.aptanet.com/ | 023 9238 0001
Registered in England | Company No: 4905028 | Registered Office:
Crawford House, Hambledon Road, Denmead, Waterlooville, Hants, PO7 6NU
From andy@??? Tue Jun 05 01:51:49 2012
Received: from andy by mail.bitfolk.com with local (Exim 4.72)
(envelope-from <andy@???>) id 1Sbiw1-0004jf-9D
for users@???; Tue, 05 Jun 2012 01:51:49 +0000
Date: Tue, 5 Jun 2012 01:51:49 +0000
From: Andy Smith <andy@???>
To: users@???
Message-ID: <20120605015149.GK11695@???>
References: <20120530190217.GB11695@???>
<20120530222751.GC11695@???>
<20120531024807.GD11695@???>
<20120531051054.GE11695@???>
<20120604082935.GA24956@???>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-ripemd160;
protocol="application/pgp-signature"; boundary="j3zO+32zXj6UcJCE"
Content-Disposition: inline
In-Reply-To: <20120604082935.GA24956@???>
OpenPGP: id=BF15490B; url=http://strugglers.net/~andy/pubkey.asc
X-URL: http://strugglers.net/wiki/User:Andy
User-Agent: Mutt/1.5.20 (2009-06-14)
X-Virus-Scanner: Scanned by ClamAV on mail.bitfolk.com at Tue,
05 Jun 2012 01:51:49 +0000
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: andy@???
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
spamd0.lon.bitfolk.com
X-Spam-Level:
X-Spam-ASN:
X-Spam-Status: No, score=-0.0 required=5.0 tests=NO_RELAYS shortcircuit=no
autolearn=disabled version=3.3.1
X-Spam-Report: * -0.0 NO_RELAYS Informational: message was not relayed via SMTP
X-SA-Exim-Version: 4.2.1 (built Mon, 22 Mar 2010 06:51:10 +0000)
X-SA-Exim-Scanned: Yes (on mail.bitfolk.com)
Subject: Re: [bitfolk] hardware problems on barbar, 1826Z and ongoing
X-BeenThere: users@???
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: Users of BitFolk hosting <users.lists.bitfolk.com>
List-Unsubscribe: <https://lists.bitfolk.com/mailman/options/users>,
<mailto:users-request@lists.bitfolk.com?subject=unsubscribe>
List-Archive: <http://lists.bitfolk.com/lurker/list/users.html>
List-Post: <mailto:users@lists.bitfolk.com>
List-Help: <mailto:users-request@lists.bitfolk.com?subject=help>
List-Subscribe: <https://lists.bitfolk.com/mailman/listinfo/users>,
<mailto:users-request@lists.bitfolk.com?subject=subscribe>
X-List-Received-Date: Tue, 05 Jun 2012 01:51:50 -0000
--j3zO+32zXj6UcJCE
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Hi Peet,
On Mon, Jun 04, 2012 at 10:29:35AM +0200, Peet Grobler wrote:
> Thank you for your decent, very verbose explanations of what is going wro=
ng. I believe this distills trust in your clients. First off, we know you k=
now what you're doing. Second - we are informed of problems, with much deta=
il, and along the process of fixing it we are informed of what you've done =
so far, and what to expect.
Thanks to you and others who have commented. Especially those who
were affected, for your understanding.
Thanks must also go to Miah Gregory who was present in our IRC
channel and offered advice on how to best recover, for several
hours. I was on basically the right track but Miah's advice sped
things up quite a bit.
Anyway this is not the last word on this matter of course. I'm still
working on a plan of action and I will get back to you in due
course. This is going to include service credit
