Happy sysadmin day to everyone. In light of that, here is a link to a classic UNIX war story that’s about 25 years old.
A few years back I got a call from one of the guys that did helpdesk and user support on my team. He said he was absolutely baffled by a problem with a laptop and wanted some advice. It was an older Dell and the apparent issue was weird lines or pattern on the screen. Naturally, I’ve asked him if the screen was hosed and apparently it wasn’t.
I was somewhat annoyed and told him to update the video drivers and he should be fine. A couple of hours later he says that the problem is still there. At this point, I am beginning to seriously doubt his technical acumen and I told him to bring the laptop over.
I took a quick look and the lines would only show up once Windows finished booting. Nothing was there during the BIOS/boot-up screens. “Obviously” it had to be some kind of a driver problem and he just screwed up the re-install somehow. So, while in my office, he started going through the process again. Remove the drivers, install the drivers, rinse and repeat. I’ve had him try Dell drivers, generic drivers, signed drivers from Microsoft and drivers from the card manufacturer. End result: the lines were still there.
Now it got somewhat interesting. There had to be a reasonable explanation. Another engineer walked by, asked what were we doing and next thing you know; 3 of us are spending hours with this laptop, trying to figure out what the hell is going on. This was a completely unproductive use of everyone’s time, but by then we just wanted to see an answer. Extensive googling yielded nothing. I was close to throwing my arms up and blaming this on the mystery computer gods or “user error”, when one of the guys shouted: “Eureka!”.
Turns out, Dell came up with a “software privacy filter”, which presumably would be a great alternative to the hardware option. This software would pixelate the screen to reduce the viewing angle. Don’t know if it really worked or not, but the user accidentally turned it on and forgot about it. We’ve wasted close to 7 man hours on this. This one could be chucked up to the category of: “it’s not a bug, it’s a feature”.
Reading the last dailywtf post brought to mind another old story from my past. I was working for a consulting/VAR company at the time and I’ve had clients ranging from Fortune 500 to small shops with <10 people. This was a really small company with a single “IT guy” that ran everything. Of course problems eventually ensued and we were called in. If I remember correctly, it was a layer 2 loop that took them down. A few hours were spent tracing the spaghetti in the so-called rack which should have given me a hint. After that I proceeded to the assessment of their networks & systems and after a little while I noticed that there were no firewalls or any kind of security on the servers themselves. They were all on public IPs and wide open to the world. I brought it up with the resident IT expert and asked him if he wasn’t worried about security. He answered that it’s all just a big waste of money and they are perfectly safe since he watches the servers all the time. I thought I found a great retort and asked what happens at night or when he is not there. His reply was an instant classic. He said that he simply turns everything off when he leaves. There wasn’t much else I could say. You can’t get more secure then that.
An old war story. I love to read those.