From owner-freebsd-questions@FreeBSD.ORG Tue Mar 22 14:15:48 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DDAFB16A4D1 for ; Tue, 22 Mar 2005 14:15:48 +0000 (GMT) Received: from trans-warp.net (hyperion.trans-warp.net [216.37.208.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4CE3A43D54 for ; Tue, 22 Mar 2005 14:15:48 +0000 (GMT) (envelope-from bsilver@chrononomicon.com) Received: from [127.0.0.1] (unverified [65.193.73.208]) by trans-warp.net (SurgeMail 2.2g3) with ESMTP id 731995 for multiple; Tue, 22 Mar 2005 09:15:45 -0500 In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v619.2) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <25a21672d1f26a7a864591057fa04250@chrononomicon.com> Content-Transfer-Encoding: 7bit From: Bart Silverstrim Date: Tue, 22 Mar 2005 09:15:38 -0500 To: "Ted Mittelstaedt" X-Mailer: Apple Mail (2.619.2) X-Server: High Performance Mail Server - http://surgemail.com X-Authenticated-User: bsilver@chrononomicon.com X-DNS-Paranoid: DNS ptr lookup of (65.193.73.208) failed cc: freebsd-questions@freebsd.org Subject: Re: Anthony's drive issues.Re: ssh password delay X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Mar 2005 14:15:49 -0000 On Mar 22, 2005, at 5:46 AM, Ted Mittelstaedt wrote: > That is also when I discovered how Microsoft gets away with telling the > world that they will fix any problem that you call into their > $250-and-incident > tech support people. If you present them with a problem they cannot > figure out, they will just ask for dump after dump, over and over, > until you get tired of it and go away. Then they mark it down to the > customer not wanting to pursue the ticket and pat themselves on the > back > and claim this must mean it was never their fault to begin with. We had a similar issue with a terminal server crashing periodically. Dump after dump sent to Dell and MS...each time they were baffled to the cause. Turned out a particular application was causing it. the users would have their terminal session "lock up", they'd restart their computer, log into a different server (or the same one, if it was restarted in time) and then keep going without telling people while we were scrambling to try diagnosing why the #@$! server restarted. After the money spent and time wasted, we ended up solving the problem ourselves and Dell and MS closed the issue.