Man, if anyone ever asks you why so many sysadmins have such a hate on for Windows (and honestly, who doesn’t want to have an answer ready for a question like that?) one of the reasons you can give them is that having to patch a whole dependency-tree full of various stuff is just a huge pain in the ass. Why won’t updates just restart the relevant services on a windows box yet? Because coming from a Unix background, man, having to restart a machine just to update a service is clearly ridiculous. But here we are! (And updating clustered machines? Damn.) Whoever you are, world, this is why I missed your party, and why I left work at three thirty in the morning to fight the dregs of halloween for a cab home.
I’m really looking forward to having centralized logging at work, so that maybe we’ll be able to tell what’s actually going on, and which of these errors are real or not; Asp.NET stuff, for example, spooges all over my logs for no apparent reason at all. Dear Programmers: Error messages should mean something, you know? When some service doesn’t start, and that’s a totally expected condition then it shouldn’t spit out errors like it’s the end of the world. And conversely! Who wants to open up their logs at three in the morning and find something that says “ASP.NET# failed to futzpop bangwarble antwerp AF03 zarqzarq: additional information in error message”, particularly when the “additional information in error message” is “00 0C”. Thanks, I’ll get right on that!
Microsoft, I’m looking at you: this is why there are so many people who hate and fear your server software, and nobody really loves it; when things go south, there’s nothing whatsoever in there to clue you in as to what’s actually gone wrong much less how to fix it. If you ever sit back in your Aerons wondering idly why your support forums are full of bizzare inquiries and quasi-superstitious suggestions (I tried these eight unrelated things, and then lit two candles! One of them worked and I don’t know why, but try them all including the candles!) this is the reason. Error messages are incredibly important public-facing information, and they’re less intelligible now than they were on NT 3.5.
I was going to direct that at Oracle too but, man, screw those guys.