2016-06-06 12:52



Say I want to execute a PHP script periodically, eg. /home/user/refresh.php, I see several options to set up the cronjob:

# Option A: PHP interpreter
*/15 * * * * php-cgi /home/user/refresh.php

# Option B: curl
*/15 * * * * curl -L -s 'http://host.com/refresh.php'

# Option C: wget
*/15 * * * * wget -q --spider http://host.com/refresh.php

What are the differences, other than PHP not requiring an URL? Are there performance considerations? And which way is usually the best? The only question I found regarding this matter does not go into detail very much, and I'd like to establish some sort of good habits or best practice.

  • 点赞
  • 写回答
  • 关注问题
  • 收藏
  • 复制链接分享
  • 邀请回答


  • dourang20110122 dourang20110122 5年前

    The primary difference is the security access of the user account calling the script. For examples B and C, the security context is executed as the web server user account. For A, it's the one belonging to the crontab owner. If you use option A with a dedicated account to this script, then you've got finer grain access control, because the webserver will likely have other security constraint requirements/extended access.

    Secondly, since you are hosting this script on a webserver at http://example.com, then you've opened up significantly more access to trigger the script. If it's desirable to provide more convenient access to run the script, then this is good. Otherwise it's not only less secure, but it's not as efficient since you also have the memory/processor overhead of running an actively listening web server if it's not already being used for other purposes.

    点赞 评论 复制链接分享