一些方法:

Export cron env and source it: Add * * * * * env > ~/cronenv to your crontab, let it run once, turn it back off, then run env - `cat ~/cronenv` /bin/sh And you are now inside a sh session which has cron's environment Bring your environment to cron You could skip above exercise and just do a . ~/.profile in front of your cron job, e.g. * * * * * . ~/.profile; your_command Use screen Above two solutions still fail in that they provide an environment connected to a running X session, with access to dbus etc. For example, on Ubuntu, nmcli (Network Manager) will work in above two approaches, but still fail in cron. * * * * * /usr/bin/screen -dm Add above line to cron, let it run once, turn it back off. Connect to your screen session (screen -r). If you are checking the screen session has been created (with ps) be aware that they are sometimes in capitals (e.g. ps | grep SCREEN) Now even nmcli and similar will fail.

创建一个cron作业，运行env并将stdout重定向到一个文件。 使用该文件和“env -”一起创建与cron作业相同的环境。

你可以运行:

env - your_command arguments

这将在空环境下运行your_command。

我发现的另一种简单方法(但可能容易出错，我仍在测试中)是在命令之前获取用户的配置文件。

编辑/etc/cron.d /脚本:

* * * * * user1 comand-that-needs-env-vars

会变成:

* * * * * user1 source ~/.bash_profile; source ~/.bashrc; comand-that-needs-env-vars

很脏，但它帮我完成了任务。是否有方法模拟登录?只是一个你可以运行的命令?Bash—登录不起作用。听起来这是更好的方法。

编辑:这似乎是一个可靠的解决方案:http://www.epicserve.com/blog/2012/feb/7/my-notes-cron-directory-etccrond-ubuntu-1110/

* * * * * root su --session-command="comand-that-needs-env-vars" user1 -l

回答https://stackoverflow.com/a/2546509/5593430展示了如何获取cron环境并将其用于您的脚本。但是请注意，环境会因所使用的crontab文件而有所不同。我创建了三个不同的cron条目，通过env >日志保存环境。这些是在Amazon Linux 4.4.35-33.55.amzn1.x86_64上的结果。

1. 使用root用户创建全局/etc/crontab

MAILTO=root
SHELL=/bin/bash
USER=root
PATH=/sbin:/bin:/usr/sbin:/usr/bin
PWD=/
LANG=en_US.UTF-8
SHLVL=1
HOME=/
LOGNAME=root
_=/bin/env

2. root用户crontab (crontab -e)

SHELL=/bin/sh
USER=root
PATH=/usr/bin:/bin
PWD=/root
LANG=en_US.UTF-8
SHLVL=1
HOME=/root
LOGNAME=root
_=/usr/bin/env

3./etc/cron.hour /脚本

MAILTO=root
SHELL=/bin/bash
USER=root
PATH=/sbin:/bin:/usr/sbin:/usr/bin
_=/bin/env
PWD=/
LANG=en_US.UTF-8
SHLVL=3
HOME=/
LOGNAME=root

最重要的是PATH, PWD和HOME不同。确保在cron脚本中设置这些以依赖稳定的环境。

一些方法:

Export cron env and source it: Add * * * * * env > ~/cronenv to your crontab, let it run once, turn it back off, then run env - `cat ~/cronenv` /bin/sh And you are now inside a sh session which has cron's environment Bring your environment to cron You could skip above exercise and just do a . ~/.profile in front of your cron job, e.g. * * * * * . ~/.profile; your_command Use screen Above two solutions still fail in that they provide an environment connected to a running X session, with access to dbus etc. For example, on Ubuntu, nmcli (Network Manager) will work in above two approaches, but still fail in cron. * * * * * /usr/bin/screen -dm Add above line to cron, let it run once, turn it back off. Connect to your screen session (screen -r). If you are checking the screen session has been created (with ps) be aware that they are sometimes in capitals (e.g. ps | grep SCREEN) Now even nmcli and similar will fail.