Talk about inane. I guess you've never taken a laptop somewhere with a different printer and wanted to .... I dunno, "print" something?

Sounds far too much like fleshlight, sorry.

"The American Third Position Party believes that government policy in the United States discriminates against white Americans, the majority population, and that white Americans need their own political party to fight this discrimination."

Your signature says that you're a racist fuckwad, regardless of your "no discrimination" claim.

US Govt? Surely you mean those crazy russians.

I've written a couple of patches for nginx. It's a giant state machine. The code is amazingly different from anything I've worked on before. I can't believe someone manually types that shit - but it all makes sense.

Yes, you're a fucking zit doctor. Congratulations.

I've run out of inodes once. Now I monitor them as well. Thankfully it was just one machine and changing the replica was simple.

They already have a Cyrus murder cluster - no need to do the LDAP routing. And they already have multiple backends. The IO issues are purely one SAN, and everything striped to spread load out so evenly that there's no spare capacity anywhere online when it runs out.

It's certainly cheapest to run that way, but running everything at 100% utilisation means no capacity to adapt to change. It's not just computer systems either - if you work all your staff at 100% utilisation all the time just to do current tasks, you're unable to adapt to change, because nobody has time to do anything else. It's the flip side of perfect efficiency - total ridigity in the face of change.

But yeah, SPOF. Most horror stories start with one of those.

nginx is not a magic bullet - it would not help in this case.

As a mail administrator for a big system, I completely agree with you.

The biggest problem was that they had everything on a single SAN, so when they ran out of IOPs, there was no spare capacity anywhere, and nowhere to mitigate it to. I've had people try to sell me on putting all our systems on a SAN too "it's so simple to administrate. It has plenty of IOPs, see, look at these shiny numbers". Fine when it's empty and you're only hitting the battery backed cache.

Which is why we have hundreds of separate little disk sets managed with templated configurations rather than any single points of failure. I'm really glad to be there!

gerber are obviously just typosquatting gerbil.xxx, a domain which I expect to retail for plenty.