论坛徽章:: 0

电梯直达

1楼 [收藏(0)] [报告]

发表于 2015-02-12 19:59 |只看该作者 |倒序浏览

crontab -e
45 18 * * *  /tmp/test1.sh

脚本
#!/bin/bash
useradd user1
echo "user1" | passwd --stdin user1 &> /dev/null
echo "Add user1 finished."

我使用crontab配置
1SHELL=/bin/bash
2 PATH=/sbin:/bin:/usr/sbin:/usr/bin
3 MAILTO=root
4 HOME=/

错误信息
X-Cron-Env: <LANG=en_US.UTF-8>
X-Cron-Env: <SHELL=/bin/sh>
X-Cron-Env: <HOME=/root>
X-Cron-Env: <PATH=/usr/bin:/bin>
X-Cron-Env: <LOGNAME=root>
X-Cron-Env: <USER=root>
Date: Tue, 10 Feb 2015 19:09:16 +0800 (CST)
Status: RO

/bin/sh:  command not found
为什么会出现这种结果是SHELL=/bin/sh这个问题吗可是配置我明明是SHELL=/bin/bash 还是其他什么问题

文库|博客

dengbao2001

腰缠万贯

论坛徽章:: 13

2楼 [报告]

发表于 2015-02-12 20:39 |只看该作者

Cron always runs with a mostly empty environment. HOME, LOGNAME, and SHELL are set; and a very limited PATH. It is therefore advisable to use complete paths to executables, and export any variables you need in your script when using cron.

There are several approaches you can use to set your environment variables in cron, but they all amount to setting it in your script.

Approach 1: Set each variable you need manually in your script.

Approach 2: Source your profile:

. $HOME/.bash_profile (or . $HOME/.profile)

(You will ususally find that the above file will source other files (e.g. ~/.bashrc --> /etc/bashrc --> /etc/profile.d/*) - if not, you can source those as well.)

Approach 3: Save your environment variables to a file (run as the desired user):

env > /path/to/my_env.sh
Then import via your cron script:

env - `cat /path/to/my_env.sh` /bin/sh
Approach 4: In some cases, you can set global cron variables in /etc/default/cron. There is an element of risk to this however, as these will be set for all cron jobs.