& at the end of the line sends the command to the background.And sends all the stdout and stderr output to the file nohup.out (by default). nohup – prevents the process from receiving SIGHUP (Signal Hang UP) signal ( source).You can кun the script mysql_import.sh in the background (instead of detaching a session) and close the Putty window: cd /var/www Other Solutions 2.1 Run the Process in the Background Please see this post for screen keyboard shortcuts.Ģ. To destroy a session, reattach the session, then press Ctrl A, then K, and then Y. Then you can reattach any session as: screen -r įor example, if the session ID is 1672, then you can reattach it as: screen -r 1672 Type 'screen -r tty.host' to resume one of them.Īlso, if you have several detached sessions, you can list them (and their IDs) with: screen -ls There are screens on:ġ2204 ( 02:01:10 AM) (Detached)ġ2204 ( 02:00:17 AM) (Detached)ġ2204 ( 01:22:31 AM) (Detached) If there are several detached sessions, the output would be like this: There are several suitable screens on:ġ2204 ( 02:01:11 AM) (Detached)ġ2204 ( 02:00:18 AM) (Detached)ġ2204 ( 01:22:32 AM) (Detached) To reattach the detached session: screen -r Check that the process is still running: ps -aux | grep mysql_import Press Ctrl A and then D to detach the session.Īlso, please see this post on detaching sessions.Ħ. One way to do it is to start a thread that does nothing than read tail's output into a large-enough buffer.5. You can access it via proc.stdout and read from it just like from a regular file.īut reading from it will probably turn out to be somewhat tricky, since you'll have to do it periodically to ensure that the pipe's buffer doesn't fill up and block the tail process. The stdout=subprocess.PIPE is here so that you have a way to read tail's output. In your case, that would be simple enough - you'd simply have to build the list of log files using python and then pass the list elements as further arguments. It's usually better to find a way that doesn't require the shell. Be careful in passing arguments to Popen with shell=True this can be a security risk if the arguments are user-supplied.

If not for that, you wouldn't need the shell. You need the shell=True so that the wildcard in *.log will be interpreted. It will look something like this: proc = subprocess.Popen(, stdout=subprocess.PIPE, shell=True) Subprocess.check_output will wait until the child process terminates and only then give you it's output.

Python subprocess background nohup