Skip to main content

How to Run Linux Commands or Shell Scripts in Background

How to Run Linux Commands or Shell Scripts in Background



When we run a command in the terminal, it will be executed on the same terminal and we have to wait or open a new session to continue our work. 
This is called running the command in the foreground or foreground process. 

A background process is a process/command that is started from a terminal and runs in the background, without interaction from the user.

Run a Linux Command in the Background

To run a command in the background, add the ampersand symbol (&) at the end of the command:


command &


The shell job ID (surrounded with brackets) and process ID will be printed on the terminal:

[1] 3507

You can have multiple processes running in the background at the same time.


The background process will continue to write messages to the terminal from which we invoked the command. To suppress the stdout and stderr messages use the following syntax:

command > /dev/null 2>&1 & 

>/dev/null 2>&1 means redirect stdout to /dev/null and stderr to stdout .


Display the running jobs in the Terminal

To display the status of all stopped and background jobs in the current shell session run the below command:

jobs -l

The output includes the job number, process ID, job state, and the command that started the job:

[1]+ 3507 Running                 ping google.com &
[2]+ 2787 Running                 /bin/bash ./while_infinite_loop.sh /dev/null 2>&1 &

To bring a background process to the foreground, use the fg command:

fg

If we have multiple background jobs, include % and the job ID after the command:


fg %1

To terminate the background process, use kill command followed by the process ID:

kill -9 3507

Move a Foreground Process to Background


To move a running foreground process in the background:

Stop the process by typing Ctrl+Z.
Move the stopped process to the background by typing bg.


To Keep Background Processes Running After a Shell Exits
Now if we close the putty or terminal session, or connection is lost then the background job will be lost.

First Method

Remove the job from the shell’s job control using the disown shell builtin:

disown

If we have more than one background jobs, include % and the job ID after the command:

disown %1

Confirm that the job is removed from the table of active jobs using the jobs -l command. 

To list all running processes, including the disowned use the ps aux command.

ps aux |grep -i command
 
Second Method

The nohup command executes another program specified as its argument and ignores all SIGHUP (hangup) signals. SIGHUP is a signal that is sent to a process when its controlling terminal is closed.

To run a command in the background using the nohup command, type:

nohup command &

The command output is redirected to the nohup.out file.

nohup: ignoring input and appending output to 'nohup.out'

If we log out or close the terminal, the process is not terminated.





If you like please follow and comment

Comments

Popular posts from this blog

WebLogic migration to OCI using WDT tool

WebLogic migration to OCI using WDT tool Oracle WebLogic Deploy Tool (WDT) is an open-source project designed to simplify and streamline the management of Oracle WebLogic Server domains. With WDT, you can export configuration and application files from one WebLogic Server domain and import them into another, making it a highly effective tool for tasks like migrating on-premises WebLogic configurations to Oracle Cloud. This blog outlines a detailed step-by-step process for using WDT to migrate WebLogic resources and configurations. Supported WLS versions Why Use WDT for Migration? When moving Oracle WebLogic resources from an on-premises environment to Oracle Cloud (or another WebLogic Server), WDT provides an efficient and reliable approach to: Discover and export domain configurations and application binaries. Create reusable models and archives for deployment in a target domain. Key Pre-Requisites Source System: An Oracle WebLogic Server with pre-configured resources such as: Applica...

How to Validate TDE Wallet Password in Oracle Database

How to Validate TDE Wallet Password in Oracle Database Validating the Transparent Data Encryption (TDE) wallet password is crucial, especially when ensuring that the password is correct without using the OPEN or CLOSE commands in the database. This blog post explains a straightforward method to validate the TDE password using the mkstore utility. Steps to Validate TDE Wallet Password Follow these steps to validate the TDE wallet password: Step 1: Copy the Keystore/Wallet File Navigate to your existing TDE wallet directory. Copy only the ewallet.p12 file to a new directory. If a cwallet.sso file exists, do not copy it . The absence of cwallet.sso ensures that the wallet does not use auto-login, forcing the utility to prompt for the password. Step 2: Validate Using mkstore Use the mkstore utility to check the contents of the wallet file. The mkstore utility will prompt you for the TDE wallet password, allowing you to validate its correctness. Command Syntax To display the conten...

EBS 12.2 ADOP Interview Questions With Scenarios

EBS 12.2 ADOP Interview Questions With Scenarios Note: Check the patch cycle log is important to fix any issues.  Location: $ADOP_LOG_HOME Useful Adop Commands Click here 1.What is ADOP concept in oracle apps Online patching is the most important new feature in Oracle E-Business Suite Release 12.2. It is the ability to patch a running system without having to take the system down for a significant period of time while the patches are applied. 'adop' is the utility we use to apply patches in R12.2 2.What is PATCH_TOP directory in R12.2 In R12.2 there is a new directory location environment variable called $PATCH_TOP which points to $NE_BASE/EBSapps/patch $NE_BASE points to <Non-Editioned-filesystem-directory> Download the patch into the patch top directory and unzip it. This is the default location where the adop will look for patch files. If you are planning to put patches in non-defualt location then you need to use adop parameter 'patchtop=<patch_path>' to...