Cant log in....again.

Its amazing that this stuff breaks so often. Oh wait, maybe not really so amazing, because at www.secondlife.com/status at this very moment, there's a 404 not found error.

Linden Labs really is populated entirely by monkeys, banging their keyboards against eachother's heads until either the problem is fixed, or Bongo the Chimp in web development deletes the status page.

Note: the status page is back up again. Still, to have a 404 on a production website even for a split second is absolutely inexcusable.

Raise your standards and your pay scale, linden.

"Logging in. Second Life may appear frozen. Please wait".

Yeah? Well it's a damn good impression of being frozen! Thanks for saying 'please' but how long should I wait exactly?

Ooooh. "Second Life is OPEN"! Great! F***ing let me in then!

Cat x

Yup. I've said it a million times and I'll say it again, the very fact that linden "labs" (ahem) chose to implement Second Life on a Linux grid system shows that they don't know what the hell they're doing. Grid systems are notorious for latency problems between nodes, and should only be used with applications that do *not* require high internode bandwidth.

This entire thing, and I'm quite serious here, having had the experience of building grid systems that broke for all the same reasons, could be fixed with about 12 million dollars of IBM or Sun equipment, and about three months of development time with a team of five people.

Yes, it sounds like a lot of money, but no, it really isn't. LL is big enough to understand that you do these kinds of expenses with layers of rolling credit, never planning to actually pay anything off. In actuality, it would only cost them in "real" money the salary of 5 expensive individuals (read: people who know exactly what they're doing) for 90 days or so, and that would come to about 350,000 USD. Peanuts, if you believe their latest profit reports.

What is pathetic is aften the open letter project and all that was said, Lindens should have at least picked up on the frustration of residents not being damn informed when things dont go to plan!

How many more times do you lindens have to listen to residents telling you the same thing? tell us whats happening, or if there is a problem damn it!

Someone came up with a good analogy recently - something about a delayed plane of irate passengers, but things calm down a bit when pilot makes announcement over intercom to settle things down.

Stop staying silent and F*&&^ing leaving us in the dark stumbling around for whats going on please!

I am also having log in problems grrrrrrrr

O/S2 FTW!

Hahahaaa....

As long as it's not linux, the kernel and common drivers of which are also notorious for their inability to handle high-bandwidth applications. If their code is as advanced as they say it is, and if they've been compiling it successfully with GCC all this time, itll work fine under multiple virtual AIX machines under Z/OS. Or, just as easily, if not more so, under one massive Sparc/Solaris 10/cluster install.

Successful...compile...GCC...Linux?
hehe

Nothing ever compiles cleanly, unless it's a "hello world" jobby.
Somethings I've had to settle on half compiled and barely working.
Still, could be worse, we could have Windows ME running the sims

Tons of things compile just fine, and with absolutely no errors whatsoever, ever, as long as the developers know how to write good code.

In fact, I just did an update of my FreeBSD machine a few nights ago and over 900 binaries were re-built using GCC automatically, and not one error in the bunch.

As long it is not a Unix derivative, which are notorious for their inability to handle real-time applications.

Hi, you don't know what a Real Time application is. RT processing is used for things like combustion management in fuel engines, robotic arms, and other things in which management of a physical device in real time needs to be very precise. Its uncommonly used for other things, true, but is not used in any sense whatsoever within any aspect of Second Life.

In the RTOS field, QNX has a pretty tight monopoly--and really no one cares. Unix is not FOR real time applications, and is never used for them.

It looks like the problem might be with pnap in san francisco. They seem to have developed a massive black hole into which packets from every direction are falling. Hooray, Linden Labs, for not knowing what the hell BGP is or now to put together contracts allowing multiple upstream providers and fail-over in case of issues just like this one.

Freakin' monkeys smackin' keyboards, man.

The only thing I know from my analyzer is a TCP checksum error from LL, lol.
Sometimes I really ask myself, why I pay so much money for an unusable sim.