cron錯(cuò)誤

xutianxia

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=/

錯(cuò)誤信息
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
為什么會(huì)出現(xiàn)這種結(jié)果 是SHELL=/bin/sh這個(gè)問題嗎 可是配置我明明是SHELL=/bin/bash 還是其他什么問題

dengbao2001

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.

dengbao2001

看看第三條

另外，看看這篇文章
   

http://www.alleft.com/sysadmin/common-cron-mistakes/

山下碼農(nóng)

1、測(cè)試一下shell是否有效。
2、你通過什么用戶來(lái)執(zhí)行crontab？