CODEWITHSUNDEEP
pythonbashshellprocess
Jasi
Jasi

Reputation: 463

Bash script that starts python script doesn't stop itself

I'm unsure if this actually is the problem, but let me explain: I have a python script that gets started by a bash script. The bash script's job is done then, but when I grep the ps aux the call is still present. 

#!/bin/bash
export http_proxy='1.2.3.4:1234'
python -u /home/user/folder/myscript.py -some Parameters >> /folder/Logfile_stout.log 2>&1

If I grep for ps aux | grep python I get the python -u /home/user/folder/myscript.py -some Parameters as a result. According to the logfile the python script closed properly. (Code to end the script is within the script itself.) The script gets started every hour and I still see all the calls from the hours before.

Thanks in advance for your help, tips or advice!

Upvotes: 0

Views: 1294

Answers (1)

gaoithe
gaoithe

Reputation: 4358

The parent bash script will remain as long as the child (python script) is running. If you start the python script running in background (add & at end of python line) then the parent will exit.

#!/bin/bash
export http_proxy='1.2.3.4:1234'
python -u /home/user/folder/myscript.py -some Parameters >> /folder/Logfile_stout.log 2>&1 &

If you examine the process list (e.g. 'ps -elf'). It will show the child (if still running). The child PPID (parent PID) will be 1(root PID) instead of the parent PID because the parent doesn't exist any more.

It could eventually be a problem if your python script never exits. You could make the parent script wait and kill the child, e.g. wait 30 secs and kill child if it is still present:

#!/bin/bash
export http_proxy='1.2.3.4:1234'
python -u /home/user/folder/myscript.py -some Parameters >> /folder/Logfile_stout.log 2>&1 &
sleep 30
jobs
kill %1
kill -9 %1
jobs

Upvotes: 2

Related Questions