X-no-Archive:yes
Yes, there are nasty things you can do to hose a 3000. Some, like Richard's
network problems are not obvious, while others, like consuming all available
disc space, well... There are known ways to prevent these things from
happening, such as setting some limits on file and group size. And in at
least some cases, there are alternatives to the so-called "Microsoft
solution" (so called because some shops plan off-hours reboots "just in
case"). As Denys has pointed out, simply accepting the idea that one should
reboot and continue more or less guarantees that you will get to use this
solution all too often.

I hope that those who are unhappy with their 3000s will be happier with
their next platforms.

Greg Stigers
http://www.cgiusa.com

--------
Richard Barker wrote
<snip> our old HP3000 969, crashed
about 10 times in the last 2 months and HP and us never found out why.  In
some cases it was because of a spool file using all the system disc space
and then the HP could never recover.

We switched to a new N4000 and have been running for 2 months and we've
already rebooted 4 times because of jobs freezing.  It seems to be related
to network problem. <snip>

HP3000 reliable, huh !

Admittedly prior to this experience I don't remember ever seeing an HP3K
crash.

and
James Ots wrote
<snip>
there was a process on our 3K
which wouldn't die and was using all the processor time, so we had to
restart the machine. That's the second time that's happened since I've been
here (nearly two years). That's terrible reliability.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *