Effective Strategies for Setting Environment Variables in Crontab

Introduction

Cron is a time-based job scheduler in Unix-like operating systems, but it runs jobs in a minimal environment that does not inherit user shell configurations. This often leads to issues where environment variables set in files like .bash_profile or .bashrc are not available during cron job execution. This article discusses effective solutions to this problem, with a focus on a robust method using wrapper scripts.

Primary Solution: Using a Wrapper Script

Based on the accepted answer, a reliable approach is to use a shell script that sets the environment before executing the actual command. This involves creating a custom environment file, such as .cronfile, and a wrapper script that sources this file and then runs the command.

For example, in the crontab, you can schedule a script:

0 * * * * /path/to/wrapper_script.sh

The wrapper script, say wrapper_script.sh, might look like:

#!/bin/bash
# Source the environment file
. /home/user/.cronfile
# Execute the command
exec /path/to/actual_command

In this script, the . /home/user/.cronfile command loads the environment variables from .cronfile, which can contain exports like export PATH=/custom/path:$PATH. The exec command replaces the shell with the command, ensuring no extra processes.

Alternative Methods

Other methods include setting environment variables directly in the crontab file, but this may not be supported in all cron implementations like cronie. For example:

LANG=en_US.UTF-8
0 * * * * echo "Hello"

However, in systems that do not support this, syntax errors may occur. Alternatively, you can set variables per command:

0 * * * * export LANG=en_US.UTF-8; echo "Hello"

Another approach is to source the user's profile in the command:

0 * * * * . /home/user/.profile; /path/to/command

Using /etc/environment is system-wide but may not be user-specific. Additionally, starting scripts with #!/bin/bash -l can load login shells, but it's less reliable.

Controlling Cron Behavior with Environment Variables

From the reference article, certain environment variables can control cron's behavior. For instance, setting PATH ensures commands are found, MAILTO controls email notifications, and SHELL changes the default shell.

PATH=/usr/local/bin:/usr/bin
MAILTO="user@example.com"
SHELL=/bin/bash
0 * * * * /path/to/command

Code Examples and Detailed Explanation

Let's consider a practical example. Suppose you have a Python script that requires a specific APP_ENV variable. Using the wrapper method:

First, create ~/.cronfile:

export APP_ENV=production
export PATH=/home/user/scripts:$PATH

Then, create wrapper.sh:

#!/bin/bash
. /home/user/.cronfile
python3 /home/user/scripts/myscript.py

In crontab:

0 2 * * * /home/user/wrapper.sh

This ensures that when the cron job runs, the environment is properly set.

Conclusion

To reliably set environment variables in crontab jobs, using a wrapper script that sources a custom environment file is the most robust method, as it avoids compatibility issues and provides clarity. While other methods exist, they may not work universally. Always test cron jobs in a similar environment to production to ensure variables are loaded correctly.