felguard

Ahh I see. Well, I'm not really skilled in PHP so I can't do any of that functions stated above. I'll ask the desk support. But while submitting my ticket, they ask for my username and password to the shared account, do I state it?

__________________
This is Sparta!

Spartans! Ah-hu!

Skipdawg

When dropping a ticket if you need to have support look at something in cPanel or WHM provide the user/password information. If not in the spaces just put in na

__________________

meephead

I actually got curious about this and decided to use my new ssh account () to monitor just how resource intensive it was. Well, after doing that, there's a possibility of two verdicts from this: a) I suck at monitoring servers and I did something wrong or b) using 'top' to monitor wget syncing nearly 5gb of data is actually more resource intensive than wget itself. Either way, I'm actually surprised. I didn't see the cpu usage on the wget process go up beyond 2% at all (most of the time below 1%), and like I said, through most of the time the process of monitoring it was actually more cpu intensive.

I should say that there were no essential changes between the archive I was syncing with and the one I was trying to update. Although, it still had to go through 5gb of files and check for changes, which it did in about 3 minutes. Originally I assumed this would be the more intensive part of the process, but now I'm not certain. I'll probably look at it again once there's a difference between the archives.

__________________
[SH103]
http://nemesia.org/

markscns

wget should not be all the CPU intensive for one or two streams at a time, but once you get 300 clients using it on a shared server, it can become a bandwidth CPU issue.

felguard

Hmm, it looks pretty complicated. I don't really need to run this cron job, so I'll forget about it. Thanks for all your help and insighs everyone.

__________________
This is Sparta!

Spartans! Ah-hu!