felguard

I'm trying to use the Cron Jobs but I'm getting the error message sent to me in my E-Mail:

/bin/sh: /usr/bin/wget: Permission denied

This is the command I'm running:

Where the **** is my path to the file.

I've tried using the command php -q, GET, and wget -O /dev/null.

Any suggestions?

__________________
This is Sparta!

Spartans! Ah-hu!

meephead

Wget is not allowed to all users by default, although if you ask through the help desk you might be able to get access to it.

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

felguard

Oh I see, kind of had a feeling it would be like that. Thank you for your help.

__________________
This is Sparta!

Spartans! Ah-hu!

felguard

Okay, on my way to submitting a ticket in the support division, it ask for my hosting's username and password. Is this the information for my cpanel account? Do they usually ask this? Just wondering.

__________________
This is Sparta!

Spartans! Ah-hu!

markscns

Or else create a PHP file that uses fopen like this:

<?php
$fp = fopen("http://www.domain.net", "r");

?>

And then use the curl in the cron job to call that PHP script. It should do the same thing you need to do.

H

Wouldn't he want to... I don't know... write the file too?

In which case I think a combination of file_get_contents() and file_put_contents() might be less code and easier? Just throwing that out there cause I've only used WGET for downloading a file to store it or work with it on the filesystem.

meephead

I'd assume it depends on what he wants to do. For example, I'd rather not use file_*_contents() for running a mirror of an archive that's like 5gb, which is what I'm doing with wget right now. You'd probably have to write some code to compare the modified dates on the files to save yourself the trouble of doing pointless tasks (getting the entire archive of files over again even though there were only a few modified files). Also, if they were large files I'm assuming that method would be really overkill.

In my opinion certain things are just better left to wget, and I'd recommend asking for it if it's one of those things.

BTW, while on the topic, does anyone know why it's not simply allowed by default? I'm just curious since I don't really see any security risks involved in allowing it as long you know what you're getting.

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

Skipdawg

If wget is at all resource intensive that may be why it is disabled by default on shared and reseller servers. Not sure I've never used it.

__________________

H

Fully agree with that. I'd never use PHP to handle the transfer of a large file. But as an alternative to using fopen... I'd use file_get_contents as it's more suited to opening a complete file rather than stepping through.

In my opinion, I'd rather people use WGET for retrieving files and disable allow_url_fopen. I'd imagine resource wise they're about the same... but it would cut back on exploits and flaws which use it to inject remote code.