that's kinda cool.. thanks for sharing.

Ok, create/consult would have been a good one to add in. I won't deny that.

@Reid-Cooper said:

That's interesting. Quotes without the escapes should make that unnecessary. Interesting way to fix it, though.

Yeah, the quotes was still showing it as a syntax error.

With so many services starting up, there is a lot of chances for things to have not all fired up yet.

@thecreativeone91 said:

@thanksajdotcom said:

@scottalanmiller said:

@thanksajdotcom said:

Ok, I'd think it'd be a simple thing to add the CentOS 6 repos, run a yum update, and allow the packages to update. What makes it not that simple?

That it does nothing. A CentOS 5 system, pointed to CentOS 6 repos will simply see the as not applying. You can't change your OS version using YUM.

Oh, I was not aware of that.

Maybe you are thinking of Minor release updates, not major release.

Yeah, must be.

15 is incorrect. It should read: 55378008
Also, useful: 773440, 0.7734, 71077345, 58008

Ok, gonna have to not read this thread while I'm sick. It's making me laugh too much!

I have a key to ours.
It is a vile, insolent, fragile, needy thing.

@tonyshowoff said:

Your new site is better than the old one, that old layout looked just like your suit, but I always assumed that wasn't an accident. It did make me think of "Count Dracula's nephew fixes computers" though.

That was not intentional. And yes, I prefer the white too.

@PSX_Defector said:

@art_of_shred said:

If it stays as is and you just "do whatever you want", it's going to end badly.

Here's a pic of AJ doing just that.

74351-whatever-I-do-what-I-want-KfEc.png

i really like the blush.

@scottalanmiller said:

Often with those choices you get PostgreSQL too, which would be my preference nine times out of ten.

You can go straight to hell. That's right, an old rivalry that I can no longer justify.

@Aaron-Studer said:

You can thank me later 😉

Hi later.

@scottalanmiller said:

My guess is that some combination of MySQL and Apache were unable to cache all of their content. You had memory being maxed out, but not over taxed, so those subsystems were not "expanding into free memory" to leverage RAM. So they were running from disk instead of from memory.

The additional of an extra CPU helps too. Rarely do workloads run ideally from a single thread. Having two threads lets there be a lot less context switching (a LOT less) while getting better cache hits.

Ok, that makes a lot of sense.

@thanksajdotcom said:

Anyways, one thing I really appreciate is that there are not and never will be private groups.

If they were truely private, how would you know about it? 🙂

@thecreativeone91 said:

@afalcon said:

@thecreativeone91
Unless your computer is hit with a virus and the files in your "backup folder" are corrupted or cryptolocked. Those changes will sync to Drive.

We've seen this way too often with our customers.

Again. I upload to it manually. There's little chance of me getting a virus like that anyway consider I don't download anything. That's how you get those. @thanksajdotcom probably gets them from his um downloads.

I'm not stupid in how I download. I am quite...selective. I'm also careful.

@MattSpeller said:

@Aaron-Studer said:

You are crazy, but I notice stuff like this too 🙂 Maybe I am crazy too? o_0

Valuable skills for pen testing. $0.02.

True that...

@PSX_Defector said:

Which a lot of the Netflix hubbub was not actually about. Comcast actually was putting traffic shaping into their pipes. Like 15 years ago. But people have rioted and screamed about that for years. Deep packet inspection is a pipe dream at the moment for ISPs bigger than your typical rural WISP. The amount of hardware and software required for it would be immense. And just doing per route shenanigans doesn't help when you have a CDN that can change the destinations on a whim.

It's a super complicated issue.

So what was the hubbub about then? I understand the peering point discussion and agree that (CDNs not withstanding) that who ever Netflix's original ISP was, that provider was probably violating their peering agreement with the rest. But that isn't Netflix's problem, that's their ISP's problem. If the ISP now needs to pay off all of it's peers because its peering usage was unfair, fine.. if they needed to pass that fee along to Netflix, again probably fine.

I'm sure I'm overly simplifying it and would love to know more about it.

Looks like the delayed start did it! Thanks!