如何在CentOS服务器上定时自动运行R脚本获取股票数据？

Hey there! Let's walk through how to set up your stock data R script to run automatically on CentOS using cron—this tool is ideal for scheduling daily (or even multiple times daily) tasks. Here's a step-by-step guide to get you up and running:

1. Verify Your R Script Works in the Command Line #

First, make sure your script runs perfectly outside of cron to avoid headaches later:

• Open a terminal and execute your script with Rscript:

  Rscript /full/path/to/your/stock_script.R
  

• Double-check that tidyquant and lubridate are installed (if not, run install.packages(c("tidyquant", "lubridate")) in an R session first).
• Pro tip: Use absolute paths for any files/directories in your script (like future database save locations) instead of relative paths—cron runs in a different working directory, so relative paths might break unexpectedly.

2. Open the Crontab Editor #

Cron uses a user-specific configuration file to manage scheduled tasks. To edit yours:

crontab -e

If this is your first time using crontab, you’ll be prompted to pick a text editor. nano is a beginner-friendly choice.

3. Write Your Cron Schedule #

Cron uses a 5-field syntax to define task timing:

分钟 小时 日 月 星期 要执行的命令

Here are tailored examples for your needs:

Example 1: Run once daily at 8 AM #

0 8 * * * /usr/bin/Rscript /full/path/to/your/stock_script.R >> /full/path/to/cron_stock_logs.log 2>&1

Example 2: Run every 6 hours (4 times daily) #

0 */6 * * * /usr/bin/Rscript /full/path/to/your/stock_script.R >> /full/path/to/cron_stock_logs.log 2>&1

Example 3: Run at specific daily times (9 AM, 12 PM, 3 PM) #

0 9,12,15 * * * /usr/bin/Rscript /full/path/to/your/stock_script.R >> /full/path/to/cron_stock_logs.log 2>&1

Key breakdown of the command:

• /usr/bin/Rscript: This is the full path to the Rscript executable. If you’re unsure where yours is, run which Rscript in the terminal to get the correct path.
• >> /full/path/to/cron_stock_logs.log 2>&1: This redirects both standard output and error messages to a log file—critical for debugging if your task fails silently.

4. Save and Verify the Task #

• In nano, press Ctrl+O to save the crontab, then Ctrl+X to exit.
• To confirm your task is scheduled, run:

  crontab -l
  

  You should see your new cron entry listed.

5. Important Notes for Reliability #

• Permissions: Ensure the user running cron (your regular account, unless using root) has read access to the R script and write access to the log file directory.
• Environment Variables: Cron runs with a minimal environment. If your script relies on specific variables (e.g., database credentials), define them directly in the crontab above your task, or store them securely in your script (avoid plaintext credentials whenever possible!).
• Test First: To validate everything works, set up a test task that runs every minute:

  */1 * * * * /usr/bin/Rscript /full/path/to/your/stock_script.R >> /full/path/to/test_log.log 2>&1
  

  Wait a minute, check the log file and confirm your data is downloaded correctly. Once verified, switch to your desired schedule.

内容的提问来源于stack exchange，提问作者TobKel