mjhjmtu

I write a bash file, which contains screen commands. This bash file is then called from a python script using subprocess. All works perfectly fine. However, the screen sessions don't close after the script has (successfully) run and stay open. This is unwanted behaviour.

Here is an example of the bash file:

#!/bin/bash
VIRTUAL_ENV_DISABLE_PROMPT=true
source generic_path/bin/activate
cd generic_directory
screen -dmS session_1
screen -S session_1 -X stuff "Rscript script_1.Rn"

I suspect, that I have to change something in the screen commands, right? Could you advise, what I have to change, so the screen session automatically close, after the script has run.

When you execute something like

screen -dmS session_1
screen -S session_1 -X stuff "Rscript script_1.Rn"

you send to the terminal (in previously created screen) the sequence of characters Rscript script_1.Rn. This way the shell will execute the command and, then, wait for the next command.

You need to execute something like Rscript script_1.R && exit to ask to the shell to exit when your command completes successfully (please, adapt to your shell syntax).

screen -dmS session_1
screen -S session_1 -X stuff "Rscript script_1.R && exitn"

In any case, there is no need to create a window and then "remote control" it. You can simply ask to screen to execute a command for you.

screen -dm Rscript script_1.R

Last but not least, to use screen to put in background a script is one of the weirdest idea I ever heard. Please use cron or at or & instead (according to your needs).

If "Rscript" is not only a random example, please read Run R script from command line.

R CMD BATCH script_1.R &

If you want to "schedule" a script, I think "Crontab" might be a good solution.
Another solution is to run the script in background mode (with &).