Home arrow BrainDump arrow Page 4 - Executing Commands with bash

4.4 Running Several Commands All at Once - BrainDump

This two-part article will explain how to launch programs in the bash shell, used with Linux and Unix operating systems. It is excerpted from chapter four of the bash Cookbook, Solutions and Examples for bash Users, written by Carl Albing, JP Vossen and Cameron Newham (O'Reilly, 2007; ISBN: 0596526784). Copyright © 2007 O'Reilly Media, Inc. All rights reserved. Used with permission from the publisher. Available from booksellers or direct from O'Reilly Media.

TABLE OF CONTENTS:
  1. Executing Commands with bash
  2. 4.2 Telling If a Command Succeeded or Not
  3. 4.3 Running Several Commands in Sequence
  4. 4.4 Running Several Commands All at Once
  5. 4.5 Deciding Whether a Command Succeeds
By: O'Reilly Media
Rating: starstarstarstarstar / 2
June 12, 2008

print this article
SEARCH DEV SHED

TOOLS YOU CAN USE

advertisement

Problem

You need to run three commands, but they are independent of each other, and donít need to wait for each other to complete.

Solution

You can run a command in the background by putting an ampersand (&) at the end of the command line. Thus, you could fire off all three jobs in rapid succession as follows:

  $ long &
 
[1] 4592
  $ medium&
  [2] 4593
  $ short
  $

Or better yet, you can do it all on one command line:

  $ long & medium & short
  [1] 4592
 
[2] 4593
  $

Discussion

When we run a command in the background (there really is no such place in Linux), all that really means is that we disconnect keyboard input from the command and the shell doesnít wait for the command to complete before it gives another prompt and accepts more command input. Output from the job (unless we take explicit action to do otherwise) will still come to the screen, so all three jobs will be interspersing output to the screen.

The odd bits of numerical output are the job number in square brackets, followed by the process ID of the command that we just started in the background. In our example, job 1 (process 4592) is the long command, and job 2 (process 4593) is medium.

We didnít put short into the background since we didnít put an ampersand at the end of the line, so bash will wait for it to complete before giving us the shell prompt (the$).

The job number or process ID can be used to provide limited control over the job. You can kill the long job withkill %1(since its job number was1). Or you could specify the process number (e.g.,kill 4592) with the same deadly results.

You can also use the job number to reconnect to a background job. Connect it back to the foreground withfg %1. But if you only had one job running in the background, you wouldnít even need the job number, justfgby itself.

If you start a job and then realize it will take longer to complete than you thought, you can pause it using Ctrl-Z, which will return you to a prompt. You can then typebgto un-pause the job so it will continue running in the background. This is basically adding a trailing&after the fact.

See Also

ē Chapter 2 on redirecting output



 
 
>>> More BrainDump Articles          >>> More By O'Reilly Media
 

blog comments powered by Disqus
escort Bursa Bursa escort Antalya eskort
   

BRAINDUMP ARTICLES

- Apple Founder Steve Jobs Dies
- Steve Jobs` Era at Apple Ends
- Google's Chrome Developer Tool Updated
- Google's Chrome 6 Browser Brings Speed to th...
- New Open Source Update Fedora 13 is Released...
- Install Linux with Knoppix
- iPad Developers Flock To SDK 3.2
- Managing a Linux Wireless Access Point
- Maintaining a Linux Wireless Access Point
- Securing a Linux Wireless Access Point
- Configuring a Linux Wireless Access Point
- Building a Linux Wireless Access Point
- Migrating Oracle to PostgreSQL with Enterpri...
- Demystifying SELinux on Kernel 2.6
- Yahoo and Microsoft Create Ad Partnership

Developer Shed Affiliates

 


Dev Shed Tutorial Topics: