@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.

I use CrashPlan PRO on a Linux machine to mount my Synology NAS via NFS and offsite my Veeam Backups.

This is a supported method of backing up a NAS.

http://support.code42.com/CrashPlan/Latest/Backup/Mounting_Networked_Storage_Or_NAS_Devices_For_Backup

cp

@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.

Looks like this is live now...

25 days ago....silly.

Today...totally worth it.

lulz

@IRJ said:

@tonyshowoff said:

@scottalanmiller said:

Tony is the new AJ.

I'm at least 10x sexier than he is.

I'd say so
halfshirtman22.jpg

lol, reminds me a bit of a character Eric Bana used to play called Poida

Haha, alright so I set up the steps today to change the port, create new user, elevate all that (as I'm sure the people who are reading this saw)

Now my error is relating to the changes I made.
I assume the two things can work successfully together?

failed to start.JPG

Im my constant posts on trying to get this going is annoying anyone just lemme know and I'll stop attempting this/asking a million questions haha

@Aaron-Studer

Gone this all done as well thanks for the tip.

@Nic said:

(F moderated) yeah, I use them! 🙂

This censorship is a (f moderated) tragedy.

@Dashrender said:

Sure, Amazon, etc might have very low latency - but they don't control your endpoint, and that is probably just as important if not more so!

Yes, your endpoint is a big deal. But Amazon has very low latency to nearly any carrier. They peer with everyone. So in a way, they almost do. Go ping Amazon and see what your latency is.

I've done this in the past, though without looking it up I couldn't tell you how. 🙂

@Sparkum That's strange, b/c I believe "enabled" is the correct entry.

“That's why PoS attacks are so viable right now, because from an attacker's point of view, [these avenues] are nearly as attractive as PCs,” Budd said.

And PoS manufacturers and programmers are total idiots most of the time and make the worst possible stuff you can imagine with literally no security at all in most cases, and in even more cases has to run as full administrator and every other terrible mistake you can imagine.

@scottalanmiller said:

Eagerly awaiting GNU/Hurd to release!

That requires actual work, instead it's much easier for Stallman to just take credit for Linux GNU/Linux. I mean it's been 30 years and he's made no progress, and plus he lives in the 1970s anyway when it comes to his views of computers, and his followers tend to be overidealistic weirdos who do things like harass people who don't release all their source code, and make excuses for his general insanity, taking advantage of others, taking credit for others' work, and just being generally disgusting and unpleasant.

It's way easier to just do talks about why you should work for free, but not him.

@Nic said:

@Hubtech All kids love log

hqdefault (1).jpg

Thanks for the share. 😄

AWESOME, good find. i'll see if i can get this working today. Thanks!!!

@art_of_shred said:

It really does work most of the time. It's difficult to make a plug and play, one size fits all product for business computing. Every environment is unique, and every admin has their own methodology to configuring their architecture (often, that is driven by general cluelessness and/or ignorance). I think that, given the diversity of what you have to be able to adapt to, the roughly 95% success rate that I have seen with incremental forever is pretty decent. The thing that makes it somewhat aggravating is that it is a proprietary mechanism that is held rather tightly. Even inside of Unitrends, there doesn't seem to be a lot of general knowledge floating around about how to fix it when it doesn't work. The algorithms that control it are basically "unknown". It's a magical thing, powered by pixie dust, and you don't mess with it; it just kinda does its thing. If you have a Unitrends support contract, and it's giving you trouble, they can help diagnose it and get it fixed. For the rest of us...

Only complaint would be that for a backup system, 95% success rate is way, way too low for it to be a recommendation. It should be a "this is really fragile but if you want to give it a shot and monitor it closely, here it is" kind of thing at that point. It's a neat idea but if it doesn't match the reliability of traditional setups, I'd think recommendations should fall to the reliable. No aspect of IT has a stronger leaning towards consistent, conservative and reliable as backups.