shell_scripts | 常用的一些 shell 脚本 | Script Programming library

You've copied your files into a different directory:

It sounds like your output is being buffered. Have you tried disabling buffering?

You can do this by setting the PYTHONUNBUFFERED environment variable in your supervisord.conf file like below:

We can capture the return code back in the shell (once BTEQ exits) and then send an email based on that return code. Something like:

Many questions here BUT:

Cron job or cron schedule is a specific set of execution instructions specifying day, time and command to execute. crontab can have multiple execution statements. And each execution statement can have many commands (i.e. per line).

What is the significance of the #!/usr/bin/bash statement?

It is a shebang. If a script is named with the path path/to/script, and it starts with the shebang line, #!/usr/bin/bash, then the program loader is instructed to run the program /usr/bin/bash and pass it the path/to/script as the first arg.

Why is it commented out?

In computing, a shebang is the character sequence consisting of the characters number sign and exclamation mark (#!) at the beginning of a script.

Is using a shell script as a proxy even necessary to run Python scripts?

In relation to the crontab? No. You can pass many commands

The documentation explicitly states that the process should be killed:

from the docs for subprocess.run:

"The timeout argument is passed to Popen.communicate(). If the timeout expires, the child process will be killed and waited for. The TimeoutExpired exception will be re-raised after the child process has terminated."

But in your case you're using shell=True, and I've seen issues like that before, because the blocking process is a child of the shell process.

I don't think you need shell=True if you decompose your arguments properly and your scripts have the proper shebang. You could try this: