CRON paths

G

GreggIrwin

Guppy
Hi there,

We recently moved to JoDoHost, and I need to set up our cron jobs now. I'm getting a "No such file or directory" email, so I think I just have a simple path error. Before just hacking things, I thought I would ask what JoDo recommends or prefers.

I tried this first:

$HOME/<domain>.com/cgi/<script>

Which resolves to this:

/hsphere/local/home/<hosting user>/<domain>.com/cgi/<script>

Then I tried a relative path, rather than absolute:

/<domain>.com/cgi/<script>

I would also like to confirm that this is the correct PHP path to use with cron jobs:

/hsphere/shared/php5/bin/php-cli /hsphere/shared/php5/bin/php-cli

Then the answer to the above path question should apply as well. e.g.:

/hsphere/shared/php5/bin/php-cli /hsphere/shared/php5/bin/php-cli $HOME/<domain>.com/<path/script>.php

Thanks!

P.S. I have tested the scripts manually via a browser, so I have confirmed that they work there.
 
/hsphere/shared/php5/bin/php-cli -q /hsphere/local/home/<your-FTP-User>/<path-to-script>

Example:
/hsphere/shared/php5/bin/php-cli -q /hsphere/local/home/myuser/example.com/cron.php
 
Thanks Tanmaya,

It looks like I have the pathing correct then. Maybe I'll open a support ticket. It may be a permissions issue as a couple PHPs are giving me a 500 result.
 
My basic cron jobs seem to be working now, with the original $HOME based path format. I don't know what would have caused the "No such file or directory" error before, but it works now.

I'm getting "Could not open input file" with PHP scripts, though the path on the files looks correct. I've tried both with and without -q, and will investigate further.
 
Next step, it was a typo in my path to the PHP files. <sigh> Let me request that on the crontab page that the command field be made as wide as possible. All the other columns can be narrower IMO, making even more room for it.
 
You must log in or register to reply here.
Back
Top