halvard@spurv.runit.sintef.no (Halvard Halvorsen) (03/15/91)
did you fellas read the signature to this guy ??? i mean : he works for tandem computers - so the reason why he asks for how to crash 'your UNIX' should be obvious ??? ;^) so next question - how do you make a tandem computer running UNIX crash ... halvard =8-) In article <690@tndsyd.oz.au>, berny@tndsyd.oz.au (Berny Goodheart) writes: |> |> I am interested in finding out known ways to make your version of UNIX |> crash. If you know of a particular application, program bug or programming |> algorithm that will guarantee to cause your UNIX Operating system to crash |> I would like to hear about it. Tell me as much info as possible i.e., what |> the machine is and what version of the OS it is, how does the problem manifest |> itself, etc. I am particularly interested in generic bugs. |> |> .===========================================================================. |> | ACSnet: berny@tndsyd.oz UUCP: uunet!munnari.oz!tndsyd.oz.au!berny | |> | INTERNET: berny@tndsyd.oz.au DOMAIN: goodheart_berny@tandem.com | |> | PSMAIL: smtpgate @comm(berny@tndsyd.oz@munnari.oz.au) | |> TANDEM Computers Incorporated 76 Berry St, North Sydney, NSW, 2060, Australia
karish@mindcraft.com (Chuck Karish) (03/15/91)
In article <1991Mar14.202237.23294@ugle.unit.no> halvard@spurv.runit.sintef.no (Halvard Halvorsen) writes: >did you fellas read the signature to this guy ??? > i mean : he works for tandem computers - so the reason why he asks for how > to crash 'your UNIX' should be obvious ??? ;^) > .===========================================================================. > | ACSnet: berny@tndsyd.oz UUCP: uunet!munnari.oz!tndsyd.oz.au!berny | > | INTERNET: berny@tndsyd.oz.au DOMAIN: goodheart_berny@tandem.com | > | PSMAIL: smtpgate @comm(berny@tndsyd.oz@munnari.oz.au) | > TANDEM Computers Incorporated 76 Berry St, North Sydney, NSW, 2060, Australia Um, yes; Tandem's business is high-availability computing. >so next question - how do you make a tandem computer running UNIX >crash ... The answer to that question would probably be more interesting to "this guy" than would answers about other computers. I talked to a couple of Tandem engineers after USENIX this January. They bragged that their systems failed the SVVS (requiring waivers) because some tests to invoke PANIC messages didn't work; Tandem UNIX doesn't crash under some of the conditions expected by AT&T. The more ways they find to crash their own computers, the happier they'll be. They'll identify more problems they can solve in the lab rather than in the field. Chuck Karish karish@mindcraft.com Mindcraft, Inc. (415) 323-9000
wht@n4hgf.Mt-Park.GA.US (Warren Tucker) (03/17/91)
In article <669020852.14148@mindcraft.com> karish@mindcraft.com (Chuck Karish) writes: >In article <1991Mar14.202237.23294@ugle.unit.no> >halvard@spurv.runit.sintef.no (Halvard Halvorsen) writes: >>did you fellas read the signature to this guy ??? >> i mean : he works for tandem computers - so the reason why he asks for how >> to crash 'your UNIX' should be obvious ??? ;^) >The answer to that question would probably be more interesting >to "this guy" than would answers about other computers. I talked >to a couple of Tandem engineers after USENIX this January. They >bragged that their systems failed the SVVS (requiring waivers) >because some tests to invoke PANIC messages didn't work; Tandem >UNIX doesn't crash under some of the conditions expected by AT&T. Umm, yeah! A friend of mind talked about his Integrity S2 being forced to crash during a demo (by removing a Large number of Important Cards from the box while it was running!). He plugged them back in and voila, a vi session repainted itself on the terminal next to him. (Flames about potential security issues **entirely** miss the point). There are many hundreds of PANICs in AT&T code. Tandem has it down to nine, all reflecting unforeseen software logic errors. They checksum pcbs and other system databases. It be righteous. ------------------------------------------------------------------------ Warren Tucker, TuckerWare emory!n4hgf!wht or wht@n4hgf.Mt-Park.GA.US "An ANSI C elephant: just like the real one, but the position, shape and length of the trunk and tail are left to the vendor's discretion." -- me
berny@tndsyd.oz.au (Berny Goodheart) (03/18/91)
In article <1991Mar14.202237.23294@ugle.unit.no>, halvard@spurv.runit.sintef.no (Halvard Halvorsen) writes: > did you fellas read the signature to this guy ??? > i mean : he works for tandem computers - so the reason why he asks for how to crash 'your UNIX' should be obvious ??? ;^) > Ah but is it? In fact, I am collecting this information for a book I am writing about Fault Tolerant UNIX. Incidentally, this is a Prentice Hall project not a TANDEM one. However, I must say all this information will be passed back to our labs to analyse, full marks for being a-lert though! > so next question - how do you make a tandem computer running UNIX > crash ... It's real simple, in real terms (that is in normal operation) you can't!!!!. The Tandem Integrity-S2 has been specifically built to withstand any "single point of failure" but if one want's to be malicious then you could log in as root and cat /etc/termcap > /dev/kmem and bingo!!. See you in alt.flame!! Berny Goodheart (Asia/Pacific Technical consultant for UNIX Systems)