Dumbarse moments: a collection.

[reddragdiva]

0. Having a server room with a row of consoles set up, one of which is a KVM-switched graphical console for our main Unix servers. You read that right. This one isn't mine, so gets number 0.

1. Using said console for actual work on the E450 that does backups once a day and DNS, NIS and license serving the rest of the time.

2. While logged into X as root. (Inhouse practice, apparently, so the root password holders can unlock each others' sessions without shutting them down. Rather than just telnetting^[1] in and killing the screen lock if you need graphical access that badly. But anyway.)

3. Then accidentally hitting the keyboard power-down button while leaning over the desk.

0. And discovering the fucking thing hasn't been disabled.

Spent ten minutes contemplating the BOFH's thoughts on the matter while it 'saves the system state' then - finally! - asked to confirm whether I really wanted to do this. Er, no, actually.

You would believe how many calls were waiting on my voicemail from users whose apps had stopped working when their 30-second^[2] license check came up. Thankfully the license daemons restarted with the rest of the system and continued as if nothing had happened.

(Of course I filed tickets on each and every call. Our job performance is measured strictly by the numbers. That many quickly-solved tickets made me look REAL busy today.)

I can't believe some fucking moron left the keyboard power switch enabled on the main fucking server. And presumably all the others.

^[1] ssh is answering the wrong security question in an environment where the geologists pass their logins around like today's funniest cubemail. And besides, it doesn't come with stock Solaris 8.

^[2] I'm guessing. But the response was ahh rapid.

Comments

[redcountess]

sounds like it was a very close shave!

BOFH answers.

[pir.livejournal.com]

You know that by default you can unlock xlock (and xlockmore, if you want a version with fewer root holes) with the root password nomatter who locked it ?

The other answer, of course, is that graphical consoles are eeeevviiiill (yes, you may need a keyboard and monitor, but they don't have to be the console).

[illdrinn.livejournal.com]

As a geek I'm in pain.

Not surprised

[blarglefiend.livejournal.com]

Prior to working with the Canadian clowns, and then getting to see up close how "scientists" (even, or especially, "computer scientists") treat systems, I'd have been ever so slightly shocked.

Now, well... It all sounds depressingly familiar. Horrifyingly, /// was a veritable pit of clues compared to most of the world.

[mr-tom.livejournal.com]

I have nothing to add to this discussion, I just wanted to add to the number of l'il South Park people in here. :-)

[lpetersson.livejournal.com]

As a techie I really have to say:
Muahahahahaaaaahahah ha.

Reminds me of some of my Doh moments :)
Servus,
Mr Eleganza

[artifx.livejournal.com]

owwwwwwwwwwwwww.

nice save on your part though :>

Re: BOFH answers.

[reddragdiva]

"You know that by default you can unlock xlock with the root password nomatter who locked it ?"

I've certainly been bludgeoned with this fact by now :-) I've just gotten used to unlocking screens from my desk with telnet.