\t<\/p>\n
\tWhen you execute a Linux command resulting in a background process, the process will be killed automatically if a controlling terminal is closed, or a ssh session is terminated. It is because a shell, which is the parent process of all background processes running in the terminal\/ssh session, sends a SIGINT to all its child processes. If you want a process to keep running after a terminal session is over, that is when\u00a0detaching a Linux process from shell<\/strong>\u00a0can help.<\/p>\n <\/p>\n \tWhen you execute a Linux command resulting in a background process, the process will be killed automatically if a controlling terminal is closed, or a ssh session is terminated. It is because a shell, which is the parent process of all background processes running in the terminal\/ssh session, sends a SIGINT to all its child processes. If you want a process to keep running after a terminal session is over, that is when\u00a0<\/span>detaching a Linux process from shell<\/strong>\u00a0can help.<\/span><\/p>\n \tHere is how you can detach a process from bash shell.<\/p>\n \tIf a given process is running in the foreground, press Ctrl+z to interrupt it.<\/p>\n \tThen run it in the background.<\/p>\n \tFinally, type\u00a0disown<\/tt>\u00a0along with job sequence number of the backgrounded job.<\/p>\n \tdisown<\/tt>\u00a0is a built-in shell command that causes a shell to not send SIGHUP to disowned child processes, thereby allowing them to continue even after the shell process is terminated. Once a background process is disowned by a shell, the process will disappear from a job list when you type\u00a0<\/span>jobs<\/tt>\u00a0command, which means that you can safely close a terminal or log out without killing the process.<\/span><\/p>\n \tWhen run without any argument,\u00a0disown<\/tt>\u00a0removes the most recent job from a job list.<\/p>\n \tNot all shells support\u00a0disown<\/tt>, unfortunately.\u00a0disown<\/tt>\u00a0is supported in\u00a0bash<\/tt>\u00a0and\u00a0zsh<\/tt>, but shells like\u00a0csh<\/tt>,\u00a0tcsh<\/tt>,\u00a0dash<\/tt>\u00a0do not support it.<\/p>\n \tBesides\u00a0disown<\/tt>, you can also use\u00a0nohup<\/tt>\u00a0to detach a Linux process from shell, but in this case, at the time of process launch.<\/p>\n \tWhile\u00a0<\/span>disown<\/tt>\u00a0prevents a closing shell from sending SIGUP signals,\u00a0<\/span>nohup<\/tt>\u00a0configures a command to ignore SIGHUP signals sent by the shell. So once any command is launched with\u00a0<\/span>nohup<\/tt>, it does not matter whether or not the shell sends out SIGHUP. Any\u00a0<\/span>nohup<\/tt>-ed command will continue to run.<\/span><\/p>\n \t$ bg<\/div>\n [1]+ my_command & <\/pre>\n
\t$ disown %1<\/div>\n \t$ nohup <my_command> &<\/div>\n
\n