SVVS requires a panic? Was: Re: CRASH your TANDEM :

[Scott Hazen Mueller]

In article <669239249.25261 at mindcraft.com> karish at mindcraft.com (Chuck Karish) writes:
>In article <6685 at auspex.auspex.com> guy at auspex.auspex.com (Guy Harris) writes:
>>AT&T has done some bogus things in the SVVS [ ... ] , but requiring that the
>>system *panic* wasn't one of them, [...]

>It sounded sort of odd to me at the time.  Perhaps I misunderstood.

I've seen no claims (to date) that Tandem broke conformance by continuing
to run when it should panic.  I do have a quote that says "There are between
800 and 1,200 places in the UNIX operating system where it can decide to
'panic' and shut down.  Brad [Tandem s/w engineer] isolated nearly 100
junctures that, collectively, are responsible for more than 85 percent of
potential failures.  He then inserted recovery code to keep the system running.
He did this while still conforming to AT&T's standard UNIX System V."

I also have no information on SVVS compliance, though the same issue of our
internal (Tandem) magazine claims in several places that we have 100%
compliance with AT&T's UNIX System V.

>The actual capabilities of Tandem's systems also sounded wildly
>improbable to one who's used to less-robust implementations.

Heh.

I've pulled out one of the CPU's, one of the fans, and on of the disk drives
on our Integrity S2 system.  No problem.

Uptime is not spectacular, a mere 58 days; I've had Sparcservers stay up
that long.  However, we've got rotten power in my building, and even an S2
won't stay up forever without mains power.  It does ride over every minor power
glitch we've had, though, smooth as silk.

Disclaimer - I work for Tandem Computers.  This is my non-work account, and
I do not speak for the company.

-- 
Scott Hazen Mueller | scott at zorch.SF-Bay.ORG or (ames|pyramid|vsi1)!zorch!scott
10122 Amador Oak Ct.| +1 408 253 6767   |Mail fusion-request at zorch.SF-Bay.ORG
Cupertino, CA  95014|Love make, not more|for emailed sci.physics.fusion digests
SF-Bay Public-Access Unix 408-996-7358/61/78/86 login newuser password public