Birmingham mumbai

[
 163 
]
Again, feel free to use whichever text editor you feel comfortable with. In the 
following examples, I'll be using 
nano
, but if you use 
vim
, just replace 
nano
 with 
vim
 
every time you see it.
Anyway, to see backgrounding in action, open up your text editor. Feel free to open 
a file or just start a blank session. (If in doubt, type 
nano
 and press 
Enter
.) With 
the text editor open, we can background it at any time by pressing 
Ctrl
 + 
z 
on our 
keyboard.
Did you see 
what happened? You were immediately taken away from your editor 
and returned to the shell so you can now get back to executing commands. You 
should have seen some output similar to the following:
[1]+ Stopped nano 
Here, we see the 
job
 number of our process, its status, and then the name of the 
process. Even though the process of your text editor shows a status of 
Stopped
, it's 
still running. You can confirm this with the following command:
ps au |grep nano 
In my case, I see the 
nano
 process running with a PID of 
43231
:
jay        43231  0.0  0.1   5468  3632 pts/0    T    11:27   0:00 nano 
At this point, I can execute additional commands, navigate around my filesystem, 
and get additional work done. When I want to bring my text editor back, I can use 
the 
fg
 command to foreground the process, which will resume it. If I have multiple 
background processes, the 
fg
 command will bring back the one I was working on 
most recently.
If you are using 
vim
 instead of 
nano
, you can only background 
vim
 
when you are 
not
 in 
insert mode
, since it captures 
Ctrl
 + 
z
 rather 
than passing it to the shell. 

---

Controlling and Managing Processes