From: surfbaud@waverider.co.uk.allyourclothes (Dave Hemming) Newsgroups: alt.humor.best-of-usenet Subject: [rec.arts.sf.written.robert-jordan] Re: TAN: Biomedical-type people (Was Re: TAN: Genetically modified foods) Date: 9 Oct 1999 23:20:18 -0000 Subject: Re: TAN: Biomedical-type people (Was Re: TAN: Genetically modified foods) From: Alistair J. R. Young Newsgroups: rec.arts.sf.written.robert-jordan On 02 Oct 1999 19:12:41 +0100, in rec.arts.sf.written.robert-jordan Alistair J. R. Young wrote: On Thu, 30 Sep 1999 21:38:23 GMT, in message <7t0l8e$me3$1@nnrp1.deja.com>, Jeff Huo praised Shub-Internet thus: ObInevitable: Fix your line lengths! > I've heard of lots of reasons > for connectivity disruptions, but > I would have to say physical > destruction of servers by fire > is a new one for me. I would imagine > (Alistair? Rob?) that this is not > covered under the standard > sys-admin training course... Course? What course? But it is in the standard sysadmin apprenticeship, such as there is a standard one - see "Systems, Halon", "Switch, Big Red", "Floor, Raised, Possessed of the Firetrap-nature" and likewise for "Ceiling, False". And in my site policy handbook - as, since the erection of the machine room wall, it is no longer possible to hear the fire alarm from inside - we have a page devoted to the particular contingency: ----------------------------------------------------------------- PROCEDURE IN THE EVENT OF FIRE ------------------------------ 1. Hit the EPO switch. 2. If the fire has not yet reached the machine room, place the current set of backup tapes (the last weekly full backup and the current differential backup) in your pockets. 3. Leave the building. If fire prevents you from leaving the building according to normal fire procedures, follow this subprocedure: a. Locate the server having the lowest replacement value. At the current time, this is the downlevel print server. b. Throw this server out of the main window, taking care both to hit the person-sized pane of glass and to ensure that the cabling is previously disconnected to avoid it interfering with the proper flight; also, minimising damage to the other servers will go down better with the insurers. c. Stand back, and take a running jump. It is advisable to gain enough speed to miss the tarmac, and try to avoid hitting the trees on the way down. d. Sue. Depending on the extent of damage, it will subsequently be necessary to follow one of Recovery Procedures 1 ("No Significant Damage After Inspection; turn the servers back on according to normal procedure, but give the filesystems an extra fsck") - 10 ("Total Lossage; send CV to agency and consult jobs section of trade magazine"). ----------------------------------------------------------------- I think this covers all possibilities fairly well, for the moment.