blocks|key|1311647|text|你应该在你的crontab中输入完整的路径。这是最安全的选择。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1311648|如果您不想这样做，您可以在程序周围放置一个包装器脚本，并在其中设置路径。|1311649|例如：|1311650|01+01+*+*+*+command|code-block|syntax|javascript|1311651|变成：|1311652|01+01+*+*+*+/full/path/to/command|1311653|此外，从cron调用的任何东西都应该非常小心它运行的程序，并可能为PATH变量设置自己的选择。|1311654|编辑：|1311655|如果您不知道命令所在的位置，那么可以从shell执行which+<command>，它会告诉您路径。|1311656|EDIT2：|1311657|因此，一旦您的程序运行，它应该做的第一件事就是将PATH和任何其他所需的变量(例如LD_LIBRARY_PATH)设置为脚本运行所需的值。|1311658|基本上，不要考虑如何修改cron环境以使其更适合您的程序/脚本-让您的脚本处理给定的环境，方法是在启动时设置一个适当的环境。|1311659|entityMap^0|6|7|0|0|0|0|0|0|4|4|X|4|0|0|Q|F|0|0|O|4|15|F|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@$9|17|A|18|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|19|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|1A|8|@]|D|@]|E|$]]|$1|J|3|K|5|L|7|1B|8|@]|D|@]|E|$M|N]]|$1|O|3|P|5|6|7|1C|8|@]|D|@]|E|$]]|$1|Q|3|R|5|L|7|1D|8|@]|D|@]|E|$M|N]]|$1|S|3|T|5|6|7|1E|8|@$9|1F|A|1G|B|C]|$9|1H|A|1I|B|C]]|D|@]|E|$]]|$1|U|3|V|5|6|7|1J|8|@]|D|@]|E|$]]|$1|W|3|X|5|6|7|1K|8|@$9|1L|A|1M|B|C]]|D|@]|E|$]]|$1|Y|3|Z|5|6|7|1N|8|@]|D|@]|E|$]]|$1|10|3|11|5|6|7|1O|8|@$9|1P|A|1Q|B|C]|$9|1R|A|1S|B|C]]|D|@]|E|$]]|$1|12|3|13|5|6|7|1T|8|@]|D|@]|E|$]]|$1|14|3|-4|5|6|7|1U|8|@]|D|@]|E|$]]]|15|$]]

You should put full paths in your <code>crontab</code>. That's the safest option. 
If you don't want to do that you can put a wrapper script around your programs, and set the PATH in there.

e.g.

<pre><code>01 01 * * * command
</code></pre>

becomes:

<pre><code>01 01 * * * /full/path/to/command
</code></pre>

Also anything called from <code>cron</code> should be be very careful about the programs it runs, and probably set its own choice for the <code>PATH</code> variable.

EDIT:

If you don't know where the command is that you want execute <code>which &lt;command&gt;</code> from your shell and it'll tell you the path. 

EDIT2:

So once your program is running, the first thing it should do is set <code>PATH</code> and any other required variable (e.g. <code>LD_LIBRARY_PATH</code>) to the values that are required for the script to run. 
Basically instead of thinking how to modify the cron environment to make it more suitable for your program/script - make your script handle the environment it's given, by setting an appropriate one when it starts.

blocks|key|1096590|text|cron作业的默认环境非常稀疏，可能与开发python脚本的环境非常不同。对于可能在cron中运行的脚本，您所依赖的任何环境都应该显式设置。在cron文件本身中，包括python可执行文件和python脚本的完整路径。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1096591|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

The default environment for cron jobs is very sparse and may be very different from the environment you develop your python scripts in. For a script that might be run in cron, any environment that you depend on should be set explicitly. In the cron file itself, include full paths to python executables and to your python scripts.

blocks|key|1096615|text|我使用了/etc/crontab。我使用vi并将所需的路径输入到此文件中，然后以根用户身份运行它。普通的crontab会覆盖您设置的路径。A+good+tutorial+on+how+to+do+this。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1096616|系统范围的cron文件如下所示：|1096617|This+has+the+username+field,+as+used+by+/etc/crontab.
#+/etc/crontab:+system-wide+crontab
#+Unlike+any+other+crontab+you+don't+have+to+run+the+`crontab'
#+command+to+install+the+new+version+when+you+edit+this+file.
#+This+file+also+has+a+username+field,+that+none+of+the+other+crontabs+do.

SHELL=/bin/sh
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin

#+m+h+dom+mon+dow+user+++command
42+6+*+*+*+++root++++run-parts+--report+/etc/cron.daily
47+6+*+*+7+++root++++run-parts+--report+/etc/cron.weekly
52+6+1+*+*+++root++++run-parts+--report+/etc/cron.monthly
01+01+*+*+1-5+root+python+/path/to/file.py|code-block|syntax|javascript|1096618|entityMap|0|LINK|mutability|MUTABLE|url|https://web.archive.org/web/20150626074155/http://unixhelp.ed.ac.uk/CGI/man-cgi?crontab%2B5^0|4|C|K|2|1X|X|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]]|D|@$9|Z|A|10|1|11]]|E|$]]|$1|F|3|G|5|6|7|12|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|13|8|@]|D|@]|E|$K|L]]|$1|M|3|-4|5|6|7|14|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|T]]]]

I used <code>/etc/crontab</code>. I used <code>vi</code> and entered in the PATHs I needed into this file and ran it as root. The normal crontab overwrites PATHs that you have set up. <a href="https://web.archive.org/web/20150626074155/http://unixhelp.ed.ac.uk/CGI/man-cgi?crontab+5" rel="noreferrer">A good tutorial on how to do this</a>.

The systemwide cron file looks like this:

<pre><code>This has the username field, as used by /etc/crontab.
# /etc/crontab: system-wide crontab
# Unlike any other crontab you don't have to run the `crontab'
# command to install the new version when you edit this file.
# This file also has a username field, that none of the other crontabs do.

SHELL=/bin/sh
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin

# m h dom mon dow user command
42 6 * * * root run-parts --report /etc/cron.daily
47 6 * * 7 root run-parts --report /etc/cron.weekly
52 6 1 * * root run-parts --report /etc/cron.monthly
01 01 * * 1-5 root python /path/to/file.py
</code></pre>

blocks|key|1096710|text|最有可能的是，cron运行在一个非常稀疏的环境中。检查cron正在使用的环境变量，方法是附加一个将env转储到文件的虚拟作业，如下所示：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1096711|*+*+*+*+*+env+>+env_dump.txt|code-block|syntax|javascript|1096712|将其与env在正常shell会话中的输出进行比较。|1096713|通过在crontab的顶部定义环境变量，可以将自己的环境变量预先添加到本地crontab。|1096714|下面是一个快速修复方法，可以将$PATH添加到当前的crontab：|1096715|#+echo+PATH=$PATH+>+tmp.cron
#+echo+>>+tmp.cron
#+crontab+-l+>>+tmp.cron
#+crontab+tmp.cron|1096716|得到的crontab看起来类似于chrissygormley的答案，路径在crontab规则之前定义。|1096717|entityMap^0|1D|3|0|0|3|3|0|0|F|5|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|Z|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|10|8|@$9|11|A|12|B|C]]|D|@]|E|$]]|$1|M|3|N|5|6|7|13|8|@]|D|@]|E|$]]|$1|O|3|P|5|6|7|14|8|@$9|15|A|16|B|C]]|D|@]|E|$]]|$1|Q|3|R|5|H|7|17|8|@]|D|@]|E|$I|J]]|$1|S|3|T|5|6|7|18|8|@]|D|@]|E|$]]|$1|U|3|-4|5|6|7|19|8|@]|D|@]|E|$]]]|V|$]]

Most likely, cron is running in a very sparse environment. Check the environment variables cron is using by appending a dummy job which dumps <code>env</code> to a file like this:

<pre><code>* * * * * env &gt; env_dump.txt
</code></pre>

Compare that with the output of <code>env</code> in a normal shell session.

You can prepend your own environment variables to the local crontab by defining them at the top of your crontab.

Here's a quick fix to prepend <code>$PATH</code> to the current crontab:

<pre><code># echo PATH=$PATH &gt; tmp.cron
# echo &gt;&gt; tmp.cron
# crontab -l &gt;&gt; tmp.cron
# crontab tmp.cron
</code></pre>

The resulting crontab will look similar to chrissygormley's answer, with PATH defined before the crontab rules.

blocks|key|1311873|text|在我的AIX+cron上，从/etc/environment获取它的环境变量，而忽略.profile中设置的内容。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1311874|编辑:我还查看了几个不同年代的Linux机器，这些机器似乎也有这个文件，所以这可能不是AIX特有的。|1311875|我使用joemaller的cron建议检查了这一点，并在编辑/etc/environment中的PATH变量前后检查了输出。|1311876|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

On my AIX cron picks up it's environmental variables from /etc/environment ignoring what is set in the .profile. 

Edit: I also checked out a couple of Linux boxes of various ages and these appear to have this file as well, so this is likely not AIX specific. 

I checked this using joemaller's cron suggestion and checking the output before and after editing the PATH variable in /etc/environment.

blocks|key|1096872|text|如果你不想在不同的地方做相同的编辑，那么大致这样做：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1096873|*+*+*+*+*+.+/home/username/.bashrc+&&+yourcommand+all+of+your+args|code-block|syntax|javascript|1096874|这个。空格，然后是.bashrc的路径和&&命令，它们是将您的环境更改放入正在运行的bash+shell的魔力。同样，如果您真的希望shell是bash，那么在您的crontab中使用一行代码也是一个好主意：|1096875|SHELL=/bin/bash|1096876|希望它能帮助一些人！|1096877|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

If you don't want to have to make the same edits in various places, then roughly do this:

<pre><code>* * * * * . /home/username/.bashrc &amp;&amp; yourcommand all of your args
</code></pre>

The . space and then the path to .bashrc and the &amp;&amp; command are the magic there to get your environment changes into the running bash shell. Too, if you really want the shell to be bash, it is a good idea to have a line in your crontab:

<pre><code>SHELL=/bin/bash
</code></pre>

Hope it helps someone!

blocks|key|1096971|text|问题|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1096972|当您从控制台运行您的脚本时，它可以工作，但是在cron中失败。|1096973|原因|1096974|您的crontab没有正确的路径变量(可能还有shell)|1096975|解决方案|1096976|添加当前shell并将路径设置为crontab|1096977|脚本为您完成此操作|1096978|#!/bin/bash
#
#+Date:+August+22,+2013
#+Author:+Steve+Stonebraker
#+File:+add_current_shell_and_path_to_crontab.sh
#+Description:+Add+current+user's+shell+and+path+to+crontab
#+Source:+http://brakertech.com/add-current-path-to-crontab
#+Github:+hhttps://github.com/ssstonebraker/braker-scripts/blob/master/working-scripts/add_current_shell_and_path_to_crontab.sh

#+function+that+is+called+when+the+script+exits+(cleans+up+our+tmp.cron+file)
function+finish+{+[+-e+"tmp.cron"+]+&&+rm+tmp.cron;+}

#whenver+the+script+exits+call+the+function+"finish"
trap+finish+EXIT

########################################
#+pretty+printing+functions
function+print_status+{+echo+-e+"\x1B[01;34m[*]\x1B[0m+$1";+}
function+print_good+{+echo+-e+"\x1B[01;32m[*]\x1B[0m+$1";+}
function+print_error+{+echo+-e+"\x1B[01;31m[*]\x1B[0m+$1";+}
function+print_notification+{+echo+-e+"\x1B[01;33m[*]\x1B[0m+$1";+}
function+printline+{+
++hr=-------------------------------------------------------------------------------------------------------------------------------
++printf+'%25s\n'+"${hr:0:${COLUMNS:-$(tput+cols)}}"
}
####################################
#+print+message+and+exit+program
function+die+{+print_error+"$1";+exit+1;+}

####################################
#+user+must+have+at+least+one+job+in+their+crontab
function+require_gt1_user_crontab_job+{
++++++++crontab+-l+&>+/dev/null
++++++++[+$?+-ne+0+]+&&+die+"Script+requires+you+have+at+least+one+user+crontab+job!"
}


####################################
#+Add+current+shell+and+path+to+user's+crontab
function+add_shell_path_to_crontab+{
++++#print+info+about+what's+being+added
++++print_notification+"Current+SHELL:+${SHELL}"
++++print_notification+"Current+PATH:+${PATH}"

++++#Add+current+shell+and+path+to+crontab
++++print_status+"Adding+current+SHELL+and+PATH+to+crontab+\nold+crontab:"

++++printline;+crontab+-l;+printline

++++#keep+old+comments+but+start+new+crontab+file
++++crontab+-l+%7C+grep+"%5E#"+>+tmp.cron

++++#Add+our+current+shell+and+path+to+the+new+crontab+file
++++echo+-e+"SHELL=${SHELL}\nPATH=${PATH}\n"+>>+tmp.cron+

++++#Add+old+crontab+entries+but+ignore+comments+or+any+shell+or+path+statements
++++crontab+-l+%7C+grep+-v+"%5E#"+%7C+grep+-v+"SHELL"+%7C+grep+-v+"PATH"+>>+tmp.cron

++++#load+up+the+new+crontab+we+just+created
++++crontab+tmp.cron

++++#Display+new+crontab
++++print_good+"New+crontab:"
++++printline;+crontab+-l;+printline
}

require_gt1_user_crontab_job
add_shell_path_to_crontab|code-block|syntax|javascript|1096979|来源|1096980|https://github.com/ssstonebraker/braker-scripts/blob/master/working-scripts/add_current_shell_and_path_to_crontab.sh|offset|length|1096981|样本输出|1096982|​|1096983|📷|atomic|1096984|1096985|entityMap|0|LINK|mutability|MUTABLE|url|1|IMAGE|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/6c1615c50fae77af833b750934e0fe7e.png|imageAlt^0|0|0|0|0|0|0|0|0|0|0|38|0|0|0|0|0|1|1|0|0^^$0|@$1|2|3|4|5|6|7|1J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|1L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|1M|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|1N|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|1O|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|1P|8|@]|9|@]|A|$]]|$1|N|3|O|5|P|7|1Q|8|@]|9|@]|A|$Q|R]]|$1|S|3|T|5|6|7|1R|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1S|8|@]|9|@$W|1T|X|1U|1|1V]]|A|$]]|$1|Y|3|Z|5|6|7|1W|8|@]|9|@]|A|$]]|$1|10|3|11|5|6|7|1X|8|@]|9|@]|A|$]]|$1|12|3|13|5|14|7|1Y|8|@]|9|@$W|1Z|X|20|1|21]]|A|$]]|$1|15|3|11|5|6|7|22|8|@]|9|@]|A|$]]|$1|16|3|-4|5|6|7|23|8|@]|9|@]|A|$]]]|17|$18|$5|19|1A|1B|A|$1C|V]]|1D|$5|1E|1A|1F|A|$1G|1H|1I|-4]]]]

<h2>Problem</h2>

Your script works when you run it from the console but fails in cron.

<h2>Cause</h2>

Your crontab doesn't have the right path variables (and possibly shell)

<h2>Solution</h2>

Add your current shell and path the crontab

<h2>Script to do it for you</h2>

<pre><code>#!/bin/bash
#
# Date: August 22, 2013
# Author: Steve Stonebraker
# File: add_current_shell_and_path_to_crontab.sh
# Description: Add current user's shell and path to crontab
# Source: http://brakertech.com/add-current-path-to-crontab
# Github: hhttps://github.com/ssstonebraker/braker-scripts/blob/master/working-scripts/add_current_shell_and_path_to_crontab.sh

# function that is called when the script exits (cleans up our tmp.cron file)
function finish { [ -e "tmp.cron" ] &amp;&amp; rm tmp.cron; }

#whenver the script exits call the function "finish"
trap finish EXIT

########################################
# pretty printing functions
function print_status { echo -e "\x1B[01;34m[*]\x1B[0m $1"; }
function print_good { echo -e "\x1B[01;32m[*]\x1B[0m $1"; }
function print_error { echo -e "\x1B[01;31m[*]\x1B[0m $1"; }
function print_notification { echo -e "\x1B[01;33m[*]\x1B[0m $1"; }
function printline { 
 hr=-------------------------------------------------------------------------------------------------------------------------------
 printf '%s\n' "${hr:0:${COLUMNS:-$(tput cols)}}"
}
####################################
# print message and exit program
function die { print_error "$1"; exit 1; }

####################################
# user must have at least one job in their crontab
function require_gt1_user_crontab_job {
 crontab -l &amp;&gt; /dev/null
 [ $? -ne 0 ] &amp;&amp; die "Script requires you have at least one user crontab job!"
}


####################################
# Add current shell and path to user's crontab
function add_shell_path_to_crontab {
 #print info about what's being added
 print_notification "Current SHELL: ${SHELL}"
 print_notification "Current PATH: ${PATH}"

 #Add current shell and path to crontab
 print_status "Adding current SHELL and PATH to crontab \nold crontab:"

 printline; crontab -l; printline

 #keep old comments but start new crontab file
 crontab -l | grep "^#" &gt; tmp.cron

 #Add our current shell and path to the new crontab file
 echo -e "SHELL=${SHELL}\nPATH=${PATH}\n" &gt;&gt; tmp.cron 

 #Add old crontab entries but ignore comments or any shell or path statements
 crontab -l | grep -v "^#" | grep -v "SHELL" | grep -v "PATH" &gt;&gt; tmp.cron

 #load up the new crontab we just created
 crontab tmp.cron

 #Display new crontab
 print_good "New crontab:"
 printline; crontab -l; printline
}

require_gt1_user_crontab_job
add_shell_path_to_crontab
</code></pre>

<h2>Source</h2>

<a href="https://github.com/ssstonebraker/braker-scripts/blob/master/working-scripts/add_current_shell_and_path_to_crontab.sh" rel="noreferrer">https://github.com/ssstonebraker/braker-scripts/blob/master/working-scripts/add_current_shell_and_path_to_crontab.sh</a>

<h2>Sample Output</h2>

<img src="https://i.stack.imgur.com/VHOro.png" alt="add_curent_shell_and_path_to_crontab.sh example output">

blocks|key|1312080|text|将路径定义添加到具有正确值的用户crontab中将有所帮助...我在顶部(注释之后和cron作业之前)填充了我的代码行：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1312081|PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin|code-block|syntax|javascript|1312082|这足以让我的所有脚本正常工作。如果需要，可以在其中包含任何自定义路径。|1312083|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Adding a PATH definition into the user crontab with correct values will help...
I've filled mine with this line on top (after comments, and before cron jobs):
<pre><code>PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
</code></pre>
And it's enough to get all my scripts working... Include any custom path there if you need to.

blocks|key|1097062|text|在我的crontab命令行之前设置PATH对我有效：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1097063|*+*+*+*+*+PATH=$PATH:/usr/local/bin:/path/to/some/thing|code-block|syntax|javascript|1097064|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Setting PATH right before the command line in my crontab worked for me:

<pre><code>* * * * * PATH=$PATH:/usr/local/bin:/path/to/some/thing
</code></pre>

blocks|key|1097102|text|如果您使用webmin，那么以下是设置PATH值的步骤：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1097103|System
++->+Scheduled+Cron+Jobs
+++++++->+Create+a+new+environment+variable
++++++++++++->+For+user:+<Select+the+user+name>
++++++++++++->+Variable+name:+PATH
++++++++++++->+Value:+/usr/bin:/bin:<your+personal+path>
++++++++++++->+Add+environment+variable:+Before+all+Cron+jobs+for+user|code-block|syntax|javascript|1097104|entityMap^0|5|6|J|4|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]|$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|S|8|@]|D|@]|E|$]]]|L|$]]

Should you use <code>webmin</code> then these are the steps how to set the <code>PATH</code> value:

<pre><code>System
 -&gt; Scheduled Cron Jobs
 -&gt; Create a new environment variable
 -&gt; For user: &lt;Select the user name&gt;
 -&gt; Variable name: PATH
 -&gt; Value: /usr/bin:/bin:&lt;your personal path&gt;
 -&gt; Add environment variable: Before all Cron jobs for user
</code></pre>

blocks|key|1312195|text|在cron中设置所需的路径|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1312196|crontab+-e|code-block|syntax|javascript|1312197|编辑:按i键|offset|length|style|CODE|1312198|PATH=/usr/local/bin:/usr/local/:or_whatever

10+*+*+*+*+your_command|1312199|保存并退出:wq|1312200|entityMap^0|0|0|4|1|0|0|5|3|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@$I|V|J|W|K|L]]|9|@]|A|$]]|$1|M|3|N|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|Y|8|@$I|Z|J|10|K|L]]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|R|$]]

Set the required PATH in your cron 

<pre><code>crontab -e
</code></pre>

Edit: Press <code>i</code>

<pre><code>PATH=/usr/local/bin:/usr/local/:or_whatever

10 * * * * your_command
</code></pre>

Save and exit <code>:wq</code>

blocks|key|1312252|text|我找到的最简单的解决方法如下所示：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1312253|*+*+*+*+*+root+su+-l+-c+command|code-block|syntax|javascript|1312254|这个示例以根用户的身份调用su，并使用用户的完整环境(包括$PATH+)启动shell，这些环境的设置就像他们已经登录一样。它在不同的发行版上工作相同，比采购.bashrc+(这对我不起作用)更可靠，并且避免了硬编码特定的路径，这可能是一个问题，如果你提供一个例子或设置工具，而不知道用户系统上的发行版或文件布局。|offset|length|style|CODE|1312255|如果您想要一个不同于根用户的用户，也可以在su之后指定用户名，但是您可能应该在su命令之前保留root参数，因为这可以确保su有足够的权限切换到您指定的任何用户。|1312256|entityMap^0|0|0|D|2|0|L|2|13|2|1B|4|1P|2|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@$I|T|J|U|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|V|8|@$I|W|J|X|K|L]|$I|Y|J|Z|K|L]|$I|10|J|11|K|L]|$I|12|J|13|K|L]]|9|@]|A|$]]|$1|O|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|P|$]]

The simplest workaround I've found looks like this:

<pre><code>* * * * * root su -l -c command
</code></pre>

This example invokes <code>su</code> as root user and starts the shell with the user's full environment, including $PATH, set as if they were logged in. It works the same on different distros, is more reliable than sourcing .bashrc (which hasn't worked for me) and avoids hardcoding specific paths which can be a problem if you're providing an example or setup tool and don't know what distro or file layout on the user's system.

You can also specify the username after <code>su</code> if you want a different user than root, but you should probably leave the <code>root</code> parameter before <code>su</code> command since this ensures <code>su</code> has sufficient privileges to switch to any user you specify.

I'm trying to get cron to call in the correct PATHs. When I run a Python script from shell the script runs fine as it uses the PATHs set in bashrc but when I use cron all the PATHs are not used from bashrc. Is there a file I can enter the PATHs into for cron like bashrc or a way to call the PATHs from bashrc?

Sorry I don't think I worded this correctly, I can get the correct script to run (meaning the PATH to the script in crontab is not the problem here), it's just when that script is running I run a build and this uses the PATHs set in <code>.bashrc</code>. When I run the script when I'm logged in, the <code>.bashrc</code> PATHs are pulled in. Since cron doesn't run in a shell per say it does not pull in <code>.bashrc</code>. Is there a way of pulling this in without having to write a bash script wrapper?

How to get CRON to call in the correct PATHs

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我正在尝试让cron调用正确的路径。当我从shell运行一个Python脚本时，该脚本运行良好，因为它使用在bashrc中设置的路径，但是当我使用cron时，所有的路径都不是从bashrc中使用的。有没有像bashrc一样可以将路径输入到cron中的文件，或者从bashrc调用路径的方法？对不起，我不认为我的措辞正确，...

问如何让CRON在正确的路径中调用
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何让CRON在正确的路径中调用EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何让CRON在正确的路径中调用
EN