Linux, cron plan should be 0 to perform every day, today is April 1, no execution, yesterday also can

CodePudding user response:

Have a great god under the guidance of

CodePudding user response:

By post, bosses, etc

CodePudding user response:

& Must write & amp; & !

CodePudding user response:

1, & amp; Is in the background, & amp; & Before is a perform OK after a
2, do not use CD... Use the full path, sh/home/work/zhuyanlu/test. The sh
Article 3, cron every statement execution then add correct or error, such as abandon all sh/home/work/zhuyanlu/test. The sh & gt;/dev/null 2 & gt; & 1
Third role is to prevent the error handling, cause the question to postfix mail, you this each one may have no problem, if the frequency is high, can lead to too many small files, finally caused the inode disk full possible case

CodePudding user response:

reference 4 floor yolyry response:

1, & amp; Is in the background, & amp; & Before is a perform OK after a
2, do not use CD... Use the full path, sh/home/work/zhuyanlu/test. The sh
Article 3, cron every statement execution then add correct or error, such as abandon all sh/home/work/zhuyanlu/test. The sh & gt;/dev/null 2 & gt; & 1
Third role is to prevent the error handling, cause the question to postfix mail, you this each one may have no problem, if the frequency is high, can lead to too many small files, finally caused the inode disk full possible case

great god, and I changed, the current situation is that the timing task successfully execute the script, but the output file is not content, but you can manually executing scripts

CodePudding user response:

reference 4 floor yolyry response:

1, & amp; Is in the background, & amp; & Before is a perform OK after a
2, do not use CD... Use the full path, sh/home/work/zhuyanlu/test. The sh
Article 3, cron every statement execution then add correct or error, such as abandon all sh/home/work/zhuyanlu/test. The sh & gt;/dev/null 2 & gt; & 1
Third role is to prevent the error handling, cause the question to postfix mail, you this each one may have no problem, if the frequency is high, can lead to too many small files, finally caused the inode disk full possible case

script is found from the database to result to TXT then, read the splicing insert statement, execution

CodePudding user response:

The source/etc/profile
Add this thing try, script execution time is without the environment variables

CodePudding user response:

And with sh -x debugging scripts, see the specific implementation process, should understand what is going wrong