cron command with an argument

[MRusty]

I have a script on my site that creates a sitemap, and I want to run it weekly. In order to prevent unauthorized use of the script, it requires a "token" when the file is called. When the cron command line reads:

/web/cgi-bin/php5 "/home/html/cgi-bin/sitemapxml.php"

I get "Incorrect Start Security Token" error, just like I am supposed to. But when the cron command line reads:

/web/cgi-bin/php5 "/home/html/cgi-bin/sitemapxml.php token=xxxxxx"

I get "Status: 404 Not Found Content-type: text/html No input file specified."

How do you properly add arguments to a cron command line? I actually have more than one that needs to be added.

[alf55]

I have a script on my site that creates a sitemap, and I want to run it weekly. In order to prevent unauthorized use of the script, it requires a "token" when the file is called. When the cron command line reads:

/web/cgi-bin/php5 "/home/html/cgi-bin/sitemapxml.php"

I get "Incorrect Start Security Token" error, just like I am supposed to. But when the cron command line reads:

/web/cgi-bin/php5 "/home/html/cgi-bin/sitemapxml.php token=xxxxxx"

I get "Status: 404 Not Found Content-type: text/html No input file specified."

How do you properly add arguments to a cron command line? I actually have more than one that needs to be added.

Since you put the following in quotes, it is treated as a single argument (and I believe you want two args):

/home/html/cgi-bin/sitemapxml.php  token=xxxxxx

If you were running it from the command line would you be executing:

/web/cgi-bin/php5   /home/html/cgi-bin/sitemapxml.php   token=xxxxxx

Then remove the quotes and use:

/web/cgi-bin/php5 /home/html/cgi-bin/sitemapxml.php   token=xxxxxx

Also realize that the environment is usually contains less when running in cron.

[MRusty]

Thank you so much alf55!

All I needed to do was remove the quotes. I have allowed my ISP's cron manager wizzrd "Browse" button to create the command line, and it screwed it up.



But I am not exactly sure what you meant by: "Also realize that the environment is usually contains less when running in cron. "

[Irithori]

He meant, that an interactive shell potentially has a different env than cron. Think $PATH, etc
So a script that runs fine manually can behave differently via cron.

[alf55]

Thanks for the reply Irithori, I could not have said it better.