diff --git a/sources/10 Linux/Unix Bash and KSH Shell Job Control Examples.md b/sources/10 Linux/Unix Bash and KSH Shell Job Control Examples.md
deleted file mode 100644
index 0cd3f9772b..0000000000
--- a/sources/10 Linux/Unix Bash and KSH Shell Job Control Examples.md
+++ /dev/null
@@ -1,287 +0,0 @@
-重出江湖 :p 翻译Ing Luox
-
-10 Linux/Unix Bash and KSH Shell Job Control Examples
-================================================================================
-
-
-Linux and Unix are multitasking operating systems i.e. a system that can run multiple tasks (process) during the same period of time. In this new blog series, I am going to list the Linux and Unix job control commands that you can use for multitasking with the Bash or Korn or POSIX shell.
-
-### What is a job control? ###
-
-Job control is nothing but the ability to stop/suspend the execution of processes (commands) and continue/resume their execution as per your requirements. This is done using your operating system and shell such as bash/ksh or POSIX shell.
-
-### Who provides a facility to control jobs? ###
-
-The Bash / Korn shell, or POSIX shell provides a facility to control jobs.
-
-### Say hello to job table ###
-
-Your shell keeps a table of current jobs, called job table. When you type command the shell assigns a jobID (also known as JOB_SPEC). A jobID or JOB_SPEC is nothing but small integer numbers.
-
-#### #1: Creating your first Linux/Unix job ####
-
-I am going to run a command called xeyes that displays two googly eyes on screen, enter:
-
- $ xeyes &
-
-Sample outputs:
-
-[][4]
-*Fig.01: Running the xeyes command in the background*
-
-I started a job in the background with an ampersand (&). The shell prints a line that looks like the following:
-
- [1] 6891
-
-In this example, two numbers are output as follows
-
-- [1] : The xeyes job, which was started in the background, was job number 1.
-- 6891 : A process ID of job number 1.
-
-I am going to start a few more jobs:
-
- ## Start a text editor, system load average display for X, and sleep command ##
- gedit /tmp/hello.c &
- xload &
- sleep 100000 &
-
-#### #2: List the current jobs ####
-
-To [see the status of active jobs in the current shell][1], type:
-
- $ jobs
- $ jobs -l
-
-Sample outputs:
-
- [1] 9379 Running xeyes &
- [2] 9380 Running gedit /tmp/hello.c &
- [3]- 9420 Running xload &
- [4]+ 9421 Running sleep 100000 &
-
-A brief description of each field is given below:
-
-(注:表格部分,这样发表出来应该会方便看一点)
-
| Field | Value | Description | Example(s) |
|---|
| 1 | [1] | jobID or JOB_SPEC - Job number to use with the fg, bg, wait, kill and other shell commands. You must prefix the job number with a percent sign (%). A plus sign (+) identifies the default or current job. A minus sign (-) identifies the previous job. | %1 fg %1 kill %2 |
| 2 | 9379 | Process ID - An identification unique number that is automatically assigned to each process when it is created on the system. | kill 9379 |
| 3 | Running | state - The state of job: Running - The job is currently running and has not been suspended by a signal. Stopped - The job was suspended.
| N/A |
| 4 | xeyes & | command - The command that was given to the shell. | script & firefox url& |
-
-You can also use ps command to list the processes running on the system:
-
- $ ps
-
-#### #3: Stop or suspend running jobs ####
-
-Hit the [Ctrl]-[Z] key or use [kill command][2] as follows:
-
- kill -s stop PID
-
-In this example, start [ping command][3] and use the Ctrl-Z key sequence to stop the ping command job:
-
-[][5]
-*Animated gif 01: Suspending ping command job*
-
-#### #4: Resume suspended/stopped job in the foreground ####
-
-Let us [resume or bring stopped ping job to the foreground][6] and make it the current job with the help of [fg command][7]. The syntax is as follows:
-
- ## Job id number 5 for ping command ##
- fg %5
-
-I can also state any job whose command line begins with the string "ping":
-
- ## %String ##
- fg %ping
-
-Sample outputs:
-
- 64 bytes from www.cyberciti.biz (75.126.153.206): icmp_req=3 ttl=53 time=265 ms
- 64 bytes from www.cyberciti.biz (75.126.153.206): icmp_req=4 ttl=53 time=249 ms
- 64 bytes from www.cyberciti.biz (75.126.153.206): icmp_req=5 ttl=53 time=267 ms
- ^C
-
-#### #5: Resume suspended/stopped job in the background ####
-
-In this example, I am going to update all installed packages on Red Hat or CentOS Linux production server using [yum command][8] background job:
-
- # yum -y update &>/root/patch.log &
-
-However, due to some reason (say load issue) I decided to stop this job for 20 minutes:
-
- # kill -s stop %yum
-
-Sample outputs:
-
- [7]+ Stopped yum -y update &>/root/patch.log &
-
-#### Restart a stopped background yum process with bg ####
-
-Now, I am going to [resume stopped the yum -y update &>/root/patch.log & job][9], type:
-
- # bg %7
-
-OR
-
- # bg %yum
-
-Sample outputs:
-
- [7]+ yum -y update &>/root/patch.log &
-
-#### #6: Kill a job / process ####
-
-To stop/kill a [yum command][10] process, enter the following [kill command][11] whose jobID was 7:
-
- # kill %7
-
-OR
-
- # kill pid
-
-Sample outputs:
-
- [7]+ Terminated yum -y update &>/root/patch.log &
-
-On Linux/FreeBSD/OS X Unix you can [use killall command to kill process by name instead of PID][12] or jobID.
-
-#### #7 Why does shell kill off all my background jobs when I logout? ####
-
-In this example, I am going to start pdfwriter.py job to generate pdf files for [this site][13] in bulk:
-
- ~/scripts/www/pdfwriter.py --profile=faq --type=clean --header=logo\
- --footer-left "nixCraft is GIT UL++++ W+++ C++++ M+ e+++ d-" \
- --footer-right "Page [of] of [total]" &
-
-As soon as I logout from shell, pdfwriter.py job will be killed by my shell. To overcome this problem use [disown shell builting command to tell the shell not to send a HUP signal][14], type:
-
- $ ~/scripts/www/pdfwriter.py --profile=faq .... &
- $ disown
- $ exit
-
-#### #8 Prevent job from being killed on logout using an external command called nohup ####
-
-You can also use [nohup command to execute jobs after you exit from a shell prompt][15]:
-
- $ nohup ~/scripts/www/pdfwriter.py --profile=faq .... &
- $ exit
-
-#### #9: Finding the PID of last job ####
-
-To find the the process ID of the most recently executed background (asynchronous) command, use bash shell special parameter $!
-
- $ gedit foo.txt &
- $ echo "PID of most recently executed background job - $!"
-
-Sample outputs:
-
- PID of most recently executed background job - 9421
-
-#### #10: Wait for job completion ####
-
-The wait command waits for given process ID or jobID (job specification) , and reports its termination status. The syntax is as follows:
-
- /path/to/large-job/command/foo &
- wait $!
- /path/to/next/job/that-is-dependents/on-foo-command/bar
-
-Here is one of my working script:
-
- #!/bin/bash
- # A shell script wrapper to create pdf files for our blog/faq section
- ########################################################################
- # init() - Must be run first
- # Purpose - Create index file in $_tmp for all our wordpress databases
- ########################################################################
- init(){
- _php="/usr/bin/php"
- _phpargs="-d apc.enabled=0"
- _base="~/scripts"
- _tmp="$_base/tmp"
- _what="$1"
- for i in $_what
- do
- [[ ! -d "$_tmp/$i" ]] && /bin/mkdir "$_tmp/$i"
- $_php $_phpargs -f "$_base/php/rawsqlmaster${i}.php" > "$_tmp/$i/output.txt"
- done
- }
-
- #####################################################
- # Without index file, we can out generate pdf files
- #####################################################
- init blog
-
- ###########################################################
- # Do not run the rest of the script until init() finished
- ###########################################################
- wait $!
-
- ## Alright, create pdf files
- ~/scripts/www/pdfwriter.py --profile=blog --type=clean --header=logo\
- --footer-left "nixCraft is GIT UL++++ W+++ C++++ M+ e+++ d-" \
- --footer-right "Page [of] of [total]"
-
-#### Linux and Unix job control command list summery ####
-
-| Command | Description | Example(s) |
|---|
| & | Put the job in the background | command & |
| %n | Set the job with the given n (number) | command %1 |
| %Word | Refer the job whose command line begins with the Word | command %yum |
| %?Word | Refer any job whose command line contains the Word | command %?ping |
%% %+ | Refer to the current job | kill %% kill %+ |
| %- | Refer to the previous job | bg %- |
CTRL-Z kill -s stop jobID | Suspend or stop the job | kill -s stop %ping |
jobs jobs -l | List the active jobs | jobs -l |
| bg | Put jobs to the background | bg %1 bg %ping |
| fg | Put job to the foreground | fg %2 fg %apt-get |
-
-#### A note about shell built-in and external commands ####
-
-Run the following type command to find out whether given command is internal or external:
-
- type -a fg bg jobs disown
-
-Sample outputs:
-
- fg is a shell builtin
- fg is /usr/bin/fg
- bg is a shell builtin
- bg is /usr/bin/bg
- jobs is a shell builtin
- jobs is /usr/bin/jobs
- disown is a shell builtin
-
-In almost all cases, you need to use shell built-in commands. All external commands such as /usr/bin/fg or /usr/bin/jobs works in a different shell environment, and can not use parent shell's environment.
-
-#### Conclusion ####
-
-I hope you enjoyed this blog post series ([rss feed][16]) and I suggest that you read the following for more information:
-
-- See our faq section for [disown command examples][17], [jobs command examples][18], [bg command examples][19], and [fg command examples][20] on Linux/Unix process management.
-- Man pages [bash(1)][21], [ksh(1)][22], [ps(1)][23], [kill(1)][24]
-- [Korn shell (ksh93) documentation][25].
-- [NU bash shell documentation][26].
-
-I am planning to add more in-depth tutorial in this series. Please let me know if you need to see specific topic in the comment section below.
-
---------------------------------------------------------------------------------
-
-via: http://www.cyberciti.biz/howto/unix-linux-job-control-command-examples-for-bash-ksh-shell/
-
-译者:[译者ID](https://github.com/译者ID) 校对:[校对者ID](https://github.com/校对者ID)
-
-本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译,[Linux中国](http://linux.cn/) 荣誉推出
-
-[1]:http://www.cyberciti.biz/faq/unix-linux-jobs-command-examples-usage-syntax/
-[2]:http://www.cyberciti.biz/faq/unix-kill-command-examples/
-[3]:http://www.cyberciti.biz/faq/unix-ping-command-examples/
-[4]:http://www.cyberciti.biz/howto/unix-linux-job-control-command-list-for-bash-ksh-shell/attachment/run-xeyes-command-in-background/
-[5]:http://www.cyberciti.biz/howto/unix-linux-job-control-command-list-for-bash-ksh-shell/attachment/suspend-unix-job-command/
-[6]:http://www.cyberciti.biz/faq/unix-linux-fg-command-examples-usage-syntax/
-[7]:http://www.cyberciti.biz/faq/unix-linux-fg-command-examples-usage-syntax/
-[8]:http://www.cyberciti.biz/faq/rhel-centos-fedora-linux-yum-command-howto/
-[9]:http://www.cyberciti.biz/faq/unix-linux-bg-command-examples-usage-syntax/
-[10]:http://www.cyberciti.biz/faq/rhel-centos-fedora-linux-yum-command-howto/
-[11]:http://www.cyberciti.biz/faq/unix-kill-command-examples/
-[12]:http://www.cyberciti.biz/faq/unix-linux-killall-command-examples-usage-syntax/
-[13]:http://www.cyberciti.biz/faq/
-[14]:http://www.cyberciti.biz/faq/unix-linux-disown-command-examples-usage-syntax/
-[15]:http://www.cyberciti.biz/tips/nohup-execute-commands-after-you-exit-from-a-shell-prompt.html
-[16]:http://www.cyberciti.biz/tutorials/practical-unixlinux-series/feed/
-[17]:http://www.cyberciti.biz/faq/unix-linux-disown-command-examples-usage-syntax/
-[18]:http://www.cyberciti.biz/faq/unix-linux-jobs-command-examples-usage-syntax/
-[19]:http://www.cyberciti.biz/faq/unix-linux-bg-command-examples-usage-syntax/
-[20]:http://www.cyberciti.biz/faq/unix-linux-fg-command-examples-usage-syntax/
-[21]:http://www.manpager.com/linux/man1/bash.1.html
-[22]:http://www.manpager.com/linux/man1/ksh.1.html
-[23]:http://www.manpager.com/linux/man1/ps.1.html
-[24]:http://www.manpager.com/linux/man1/kill.1.html
-[25]:http://www2.research.att.com/sw/download/man/man1/ksh.html
-[26]:https://www.gnu.org/software/bash/manual/bashref.html
diff --git a/translated/10 Linux/Unix Bash and KSH Shell Job Control Examples.md b/translated/10 Linux/Unix Bash and KSH Shell Job Control Examples.md
new file mode 100644
index 0000000000..30c011146a
--- /dev/null
+++ b/translated/10 Linux/Unix Bash and KSH Shell Job Control Examples.md
@@ -0,0 +1,284 @@
+10个 Linux/Unix下 Bash和KSH shell 的作业控制实例
+================================================================================
+
+
+Linux 和 Unix 属于多任务的操作系统,也就是说一个系统在同一时间段内能运行多重任务(进程)。在这个新的博客系列,我将会列出相关的 Linux和Unix作业控制的命令,你可以通过这些命令在 Bash 或 Korn 还有 POSIX shell 下实现执行多重任务。
+
+### 什么是作业控制?###
+
+作业控制不过是能够停止/挂起(stop/suspend)正在执行的进程(命令)也可以继续/唤醒(continue/resume)你需要的每一个进程来执行。这完全可以用你的操作系统和类似 bash/ksh 或 POSIX shell 完成。
+
+### 谁提供给了作业控制的设施条件 ###
+
+Bash / Korn shell,或者是 POSIX shell 提供给了作业控制的设施条件。
+
+### 跟作业表打个招呼吧 ###
+
+你的 shell 会留有一张当前作业的表单,称为作业表。当你键入命令时,shell 会给它分配一个 jobID(也称作 JOB_SPEC)。一个 jobID 或 JOB_SPEC只是很小的整数数值。
+
+#### #1: 创建你的首个 Linux/Unix 作业(job) ####
+
+我要运行一个名为 xeyes 的命令,它会在屏幕上显示两个椭圆的眼睛,输入:
+ $ xeyes &
+
+输出样例:
+
+[][4]
+*Fig.01: 在后台运行 xeyes 命令*
+
+我使用&符号让一个 job 在后台运行。shell 会打印一行信息类似如下:
+
+ [1] 6891
+
+在这个例子中,有两个数字输出,分别表示:
+
+- [1] : 在后台执行的 xeyes 任务的作业号为 1。
+- 6891 : 作业1的进程ID。
+
+我在多执行一些 job:
+
+ ## 启动一个文本编辑器,X 的系统负载显示,和 sleep 命令 ##
+ gedit /tmp/hello.c &
+ xload &
+ sleep 100000 &
+
+#### #2: 列出当前的jobs ####
+
+To [see the status of active jobs in the current shell][1], type:
+
+ $ jobs
+ $ jobs -l
+
+输出样例:
+
+ [1] 9379 Running xeyes &
+ [2] 9380 Running gedit /tmp/hello.c &
+ [3]- 9420 Running xload &
+ [4]+ 9421 Running sleep 100000 &
+
+A brief description of each field is given below:
+
+(注:表格部分,这样发表出来应该会方便看一点)
+| 字段 | 值 | 描述 | 示例 |
|---|
| 1 | [1] | jobID 或 JOB_SPEC - 工作号要与fg, bg, wait, kill和其他shell命令一起使用。你必须在工作号前缀添加一个百分号。(%). 加号 (+) 标识着默认的或是现在的 job。 减号 (-) 标识着先前的 job。 | %1 fg %1 kill %2 |
| 2 | 9379 | 进程 ID - 系统自动为每个进程创建并分配地独有的身份标志号。 | kill 9379 |
| 3 | Running | 状态 - 关于 job 的状态: Running - 该 job 正在运行,还没有被外部信号挂起。 Stopped - 该 job 已经被挂起。
| N/A |
| 4 | xeyes & | command - 由shell给出的命令。 | script & firefox url& |
+
+你也可以用 ps 命名列出当前系统正在运行的进程:
+
+ $ ps
+
+#### #3: 停止或挂起正在运行的jobs ####
+
+按下[Ctrl]-[Z]键或使用[kill 命令][2],如下所示:
+
+ kill -s stop PID
+
+举个例子,启动[ping 命令][3],然后用 Ctrl-Z 键触发停止 ping 命令的job:
+
+[][5]
+*Animated gif 01: 挂起 ping 命令的 job*
+
+#### #4: 在前台恢复 挂起的/停止的 job ####
+
+让我们[恢复处于停止状态下的 job 回到前台运行][6],要实现这个目标当前 job 必须借助[fg 命令][7]。具体语法如下:
+
+ ## ping 命令的作业号的值为5 ##
+ fg %5
+
+我也可以规定命令行开端符合字符串"ping"的 job[译注:不能出现不明确的字符串,例如如果后台有两个 vim 进程而你敲入 fg %vim 会报错。]:
+
+ ## %String ##
+ fg %ping
+
+输出样例:
+
+ 64 bytes from www.cyberciti.biz (75.126.153.206): icmp_req=3 ttl=53 time=265 ms
+ 64 bytes from www.cyberciti.biz (75.126.153.206): icmp_req=4 ttl=53 time=249 ms
+ 64 bytes from www.cyberciti.biz (75.126.153.206): icmp_req=5 ttl=53 time=267 ms
+ ^C
+
+#### #5: 在后台恢复 挂起/停止状态的 job ####
+
+在这个例子中,我将要使用[yum 命令][8]更新所有安装在 Redhat 或 CentOS Linux 生产服务器上的软件包并置于后台作业。
+
+ # yum -y update &>/root/patch.log &
+
+然而,由于一些原因(例如,过载问题)我决定停止这个 job 20分钟:
+
+ # kill -s stop %yum
+
+输出样例:
+
+ [7]+ Stopped yum -y update &>/root/patch.log &
+
+#### 用 bg 重启停止在后台的 yum 进程 ####
+
+现在,我将要[恢复停止的 yum -y update &>/root/patch.log & job][9],键入:
+
+ # bg %7
+
+或者:
+
+ # bg %yum
+
+输出样例:
+
+ [7]+ yum -y update &>/root/patch.log &
+
+#### #6: 杀死作业/进程 ####
+
+杀死[yum 命令][10]进程,输入如下[kill 命令][11]及其作业号 7:
+
+ # kill %7
+
+或者
+
+ # kill pid
+
+输出样例:
+
+ [7]+ Terminated yum -y update &>/root/patch.log &
+
+在 Linux/FreeBSD/OS X Unix 下你可以[使用 killall 命令通过名字杀死进程或是 jobID 而不是通过 PID][12]
+
+#### #7 为什么当我登出后 shell 会清除我的所有后台 jobs ####
+
+在这个例子中,我将会启动 pdfwriter.py 来生成[这个站点][13]散装地 pdf 文件:
+
+ ~/scripts/www/pdfwriter.py --profile=faq --type=clean --header=logo\
+ --footer-left "nixCraft is GIT UL++++ W+++ C++++ M+ e+++ d-" \
+ --footer-right "Page [of] of [total]" &
+
+一旦当我登出shell时,pdfwriter.py 作业就会被我的 shell 杀死。为了克服这个问题需要使用[shell的内置命令 disown 来告诉 shell 不要发送 HUP 信号][14],键入:
+
+ $ ~/scripts/www/pdfwriter.py --profile=faq .... &
+ $ disown
+ $ exit
+
+#### #8 使用一个名为 nohup 的外部命令阻止在登出时杀死 job ####
+
+你也可以使用[nohup 命令在你退出 shell 后执行 jobs][15]:
+
+ $ nohup ~/scripts/www/pdfwriter.py --profile=faq .... &
+ $ exit
+
+#### #9: 查找最后 job 的 PID ####
+
+为了查找最近在后台执行的(异步)命令的进程ID,可使用 bash shell 的特殊参数 $!
+
+ $ gedit foo.txt &
+ $ echo "最近在后台执行的job 的PID - $!"
+
+输出样例:
+
+ 最近在后台执行的job 的PID - 9421
+
+#### #10: 等候 job 完成 ####
+
+wait 命令会等候给予的进程ID 或 作业ID,然后报告它的终止状态。语法如下:
+
+ /path/to/large-job/command/foo &
+ wait $!
+ /path/to/next/job/that-is-dependents/on-foo-command/bar
+
+这是我的一个工作脚本:
+
+ #!/bin/bash
+ # A shell script wrapper to create pdf files for our blog/faq section
+ ########################################################################
+ # init() - Must be run first
+ # Purpose - Create index file in $_tmp for all our wordpress databases
+ ########################################################################
+ init(){
+ _php="/usr/bin/php"
+ _phpargs="-d apc.enabled=0"
+ _base="~/scripts"
+ _tmp="$_base/tmp"
+ _what="$1"
+ for i in $_what
+ do
+ [[ ! -d "$_tmp/$i" ]] && /bin/mkdir "$_tmp/$i"
+ $_php $_phpargs -f "$_base/php/rawsqlmaster${i}.php" > "$_tmp/$i/output.txt"
+ done
+ }
+
+ #####################################################
+ # Without index file, we can out generate pdf files
+ #####################################################
+ init blog
+
+ ###########################################################
+ # Do not run the rest of the script until init() finished
+ ###########################################################
+ wait $!
+
+ ## Alright, create pdf files
+ ~/scripts/www/pdfwriter.py --profile=blog --type=clean --header=logo\
+ --footer-left "nixCraft is GIT UL++++ W+++ C++++ M+ e+++ d-" \
+ --footer-right "Page [of] of [total]"
+
+#### Linux 和 Unix 作业控制命令总结列表 ####
+
+| 命令 | 描述 | 示例 |
|---|
| & | 将 job 置入后台 | 命令 & |
| %n | 设置作业号为 n (数字)的 job | 命令 %1 |
| %Word | 引用命令行开端包含 Word 的 job | 命令 %yum |
| %?Word | 引用命令行包含 Word 的 job | 命令 %?ping |
%% %+ | 引用当前 job | kill %% kill %+ |
| %- | 引用先前 job | bg %- |
CTRL-Z kill -s stop jobID | 挂起或停止 job | kill -s stop %ping |
jobs jobs -l | 列出活动的 jobs | jobs -l |
| bg | 将 jobs 置入后台 | bg %1 bg %ping |
| fg | 将 job 置入前台 | fg %2 fg %apt-get |
+
+#### 关于 shell 内置命令和外部命令的小注 ####
+
+运行下面的 type 命令找出给予命令是否属于内部或外部的。
+
+ type -a fg bg jobs disown
+
+输出样式:
+
+ fg is a shell builtin
+ fg is /usr/bin/fg
+ bg is a shell builtin
+ bg is /usr/bin/bg
+ jobs is a shell builtin
+ jobs is /usr/bin/jobs
+ disown is a shell builtin
+
+在几乎所有情况下,你都需要使用 shell 的内置命令。所有外部命令例如 /usr/bin/fg 或 /usr/bin/jobs 工作在一个不同的 shell 环境下,而不能用在父 shell 的环境下。
+
+#### 总结 ####
+
+我希望你能喜欢这篇博文系列([rss 订阅][16]),我建议你阅读下面的更多信息:
+
+- 在我们的 faq 章节查阅有关进程管理的文章[disoen 命令示例][17],[jobs 命令示例][18],[bg 命令示例][19],和[fg 命令示例][20]。
+- Man pages [bash(1)][21], [ksh(1)][22], [ps(1)][23], [kill(1)][24]
+- [Korn shell (ksh93) 文档][25].
+- [NU bash shell 文档][26].
+
+我会计划在这个系列添加更多深入的教程。若果你需要看到具体的主题,请在下方评论让我知道。
+
+--------------------------------------------------------------------------------
+
+via: http://www.cyberciti.biz/howto/unix-linux-job-control-command-examples-for-bash-ksh-shell/
+
+译者:[Luoxcat](https://github.com/Luoxcat) 校对:[校对者ID](https://github.com/校对者ID)
+
+本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译,[Linux中国](http://linux.cn/) 荣誉推出
+
+[1]:http://www.cyberciti.biz/faq/unix-linux-jobs-command-examples-usage-syntax/
+[2]:http://www.cyberciti.biz/faq/unix-kill-command-examples/
+[3]:http://www.cyberciti.biz/faq/unix-ping-command-examples/
+[4]:http://www.cyberciti.biz/howto/unix-linux-job-control-command-list-for-bash-ksh-shell/attachment/run-xeyes-command-in-background/
+[5]:http://www.cyberciti.biz/howto/unix-linux-job-control-command-list-for-bash-ksh-shell/attachment/suspend-unix-job-command/
+[6]:http://www.cyberciti.biz/faq/unix-linux-fg-command-examples-usage-syntax/
+[7]:http://www.cyberciti.biz/faq/unix-linux-fg-command-examples-usage-syntax/
+[8]:http://www.cyberciti.biz/faq/rhel-centos-fedora-linux-yum-command-howto/
+[9]:http://www.cyberciti.biz/faq/unix-linux-bg-command-examples-usage-syntax/
+[10]:http://www.cyberciti.biz/faq/rhel-centos-fedora-linux-yum-command-howto/
+[11]:http://www.cyberciti.biz/faq/unix-kill-command-examples/
+[12]:http://www.cyberciti.biz/faq/unix-linux-killall-command-examples-usage-syntax/
+[13]:http://www.cyberciti.biz/faq/
+[14]:http://www.cyberciti.biz/faq/unix-linux-disown-command-examples-usage-syntax/
+[15]:http://www.cyberciti.biz/tips/nohup-execute-commands-after-you-exit-from-a-shell-prompt.html
+[16]:http://www.cyberciti.biz/tutorials/practical-unixlinux-series/feed/
+[17]:http://www.cyberciti.biz/faq/unix-linux-disown-command-examples-usage-syntax/
+[18]:http://www.cyberciti.biz/faq/unix-linux-jobs-command-examples-usage-syntax/
+[19]:http://www.cyberciti.biz/faq/unix-linux-bg-command-examples-usage-syntax/
+[20]:http://www.cyberciti.biz/faq/unix-linux-fg-command-examples-usage-syntax/
+[21]:http://www.manpager.com/linux/man1/bash.1.html
+[22]:http://www.manpager.com/linux/man1/ksh.1.html
+[23]:http://www.manpager.com/linux/man1/ps.1.html
+[24]:http://www.manpager.com/linux/man1/kill.1.html
+[25]:http://www2.research.att.com/sw/download/man/man1/ksh.html
+[26]:https://www.gnu.org/software/bash/manual/bashref.html