Hi
I've calmed down a bit now.
In every case HP were involved and nearly every case it involved a patch to
solve the problem. One case in particular where a DNS entry on our network
caused the HP to crash, we needed a direct change to a Binary in the
operating system. The last couple of crashes were because the engineers
investigating the problems switched the console to an LDEV that didn't
exist, after a few hours the buffer filled up and the machine crashed again.
Why does the HP allow you to switch the console to a device that isn't
active, when this can cause such a problem.
I have lots of issues with all of this. For me the point of paying the
money we did for an HP, is you receive a stable, well tested, reliable
machine with good support. I don't expect to receive a machine that needs a
service pack every week. It's all very well saying you need to apply
patches, but to me that shows a big weakness in the OS.
The other problem, is the crashes themselves, surely a machine like this
should be able at least to issue an error message or cope with most
circumstances, not just freeze like a MS OS.
The bottom line for me, is I can't get a good Server and install Linux on it
and I don't believe it will be any less stable than the HP and because of
the huge difference in cost I can afford to have a cluster, which will
eliminate most problems with downtime.
Anyway, thanks to most of you for not 'having a go', obviously with this
being an HP3000 list, I thought I might put a few 'noses out of joint', but
everyone was quite polite.
Regards
Richard
-----Original Message-----
From: Roy Brown [mailto:[log in to unmask]]
Sent: 30 July 2002 22:29
To: [log in to unmask]
Subject: Re: [HP3000-L] Reliability - myth
In message <[log in to unmask]>, Cecile Chi
<[log in to unmask]> writes
>In a message dated 7/30/02 5:04:20 AM Eastern Daylight Time,
>[log in to unmask] writes:
>
><< Tell me, is this because of the HP's lack of support for the machine, is
it
> the newer machines, or am I just very unlucky.
> >>
>
>I suspect you're just unlucky. It sounds like you got a lemon. Our N4000
>has not had any problems. We had a really odd problem involving the SORT
>intrinsic parameters that caused the 969 to crash, but the same program ran
>fine on the N4000 (both on 7.1). HP Support was very good.
I don't think that hardware lemons respond to software patches, do they?
How many of the nine crashes went unexplained by HP, or were rectified
by hardware changes?
--
Roy Brown Kelmscott Ltd
'It's that time of the year again! Your out-of-office reply should not
respond
to HP3000-L postings; and if it does, it should respond to the List Admin,
not individual posters like me. But I am prepared to check for this latter
eventuality for a processing fee of only $50.00. By sending me such a
reply, you agree to contract for this service.'
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
