From 11c001a5f3becc1e0d160551951fc9266cb42ccf Mon Sep 17 00:00:00 2001 From: tille <> Date: Mon, 23 Oct 2006 09:23:12 +0000 Subject: [PATCH] more DocBook tags --- LDP/guide/docbook/Intro-Linux/chap4.xml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/LDP/guide/docbook/Intro-Linux/chap4.xml b/LDP/guide/docbook/Intro-Linux/chap4.xml index 7a502fb7..435d17fc 100644 --- a/LDP/guide/docbook/Intro-Linux/chap4.xml +++ b/LDP/guide/docbook/Intro-Linux/chap4.xml @@ -40,7 +40,7 @@ billy:~> jobsjobs [1]+ Running xterm & -The full job control features are explained in detail in the bash Info pages, so only the frequently used job controlBashjob control applications are listed hereprocessesjob control overview: +The full job control features are explained in detail in the bash Info pages, so only the frequently used job controlBashjob control applications are listed hereprocessesjob control overview: Controlling processes @@ -225,7 +225,7 @@ init-+-amd |-xfs `-xinetd-ipv6 -The and options give additional information. For more options and what they do, refer to the Info pages. +The and options give additional information. For more options and what they do, refer to the Info pages. In the next section, we will see how one process can create another. @@ -254,7 +254,7 @@ init-+-amd Ending processes When a processprocessesending ends normally (it is not killed or otherwise unexpectedly interrupted), the program returns its exit statusexit status to the parent. This exit status is a number returned by the program providing the results of the program's execution. The system of returning information upon executing a job has its origin in the C programming language in which UNIX has been written. -The return codesprocessesreturn codes can then be interpreted by the parent, or in scripts. The values of the return codes are program-specific. This information can usually be found in the man pages of the specified program, for example the grep command returns -1 if no matches are found, upon which a message on the lines of "No files found" can be printed. Another example is the Bash Builtin command true, which does nothing except return an exit status of 0, meaning success. +The return codesprocessesreturn codes can then be interpreted by the parent, or in scripts. The values of the return codes are program-specific. This information can usually be found in the man pages of the specified program, for example the grep command returns -1 if no matches are found, upon which a message on the lines of No files found can be printed. Another example is the Bash builtin command true, which does nothing except return an exit status of 0, meaning success. Signals Processes endprocessesstopping because they receive a signalprocessessignal. There are multiple signals that you can send to a process. Use the killkill command to send a signal to a process. The command kill shows a list of signals. Most signals are for internal use by the system, or for programmers when they write code. As a user, you will need the following signalssignalsoverview: @@ -340,7 +340,7 @@ Message from joe@lo.callhost.org on ptys/1 at 12:36 ... hey Jenny, shall we have lunch together? EOF -After receiving a message, the terminal can be cleared using the Ctrl+L key combination. In order to receive no messages at all (except from the system administrator), use the mesg command. To see which connected users accept messages from others use who . All features are fully explained in the Info pages of each command. +After receiving a message, the terminal can be cleared using the Ctrl+L key combination. In order to receive no messages at all (except from the system administrator), use the mesg command. To see which connected users accept messages from others use who . All features are fully explained in the Info pages of each command. Group names may vary The group scheme is specific to the distribution. Other distributions may use other names or other solutions. @@ -696,8 +696,8 @@ job 2 at 2001-06-14 02:00 Cron and crontab The cron system is managed by the cron daemondaemonscron. It gets information about which programs and when they should run from the system's and users' crontabschedulingcron entries. Only the root user has access to the system crontabs, while each user should only have access to his own crontabs. On some systems (some) users may not have access to the cron facility. At system startup the cron daemon searches /var/spool/cron/ for crontab entries which are named after accounts in /etc/passwd, it searches /etc/cron.d/cron.d and it searches /etc/crontabcrontab, then uses this information every minute to check if there is something to be done. It executes commands as the user who owns the crontab file and mails any output of commands to the owner. -On systems using VixiecronVixie cron cron, jobs that occur hourly, daily, weekly and monthly are kept in separate directories in /etc to keep an overview, as opposed to the standard UNIX cron function, where all tasks are entered into one big file. -Example of a Vixie crontabcrontabexample file: +On systems using VixiecronVixie cron cron, jobs that occur hourly, daily, weekly and monthly are kept in separate directories in /etc to keep an overview, as opposed to the standard UNIX cron function, where all tasks are entered into one big file. +Example of a Vixie crontabcrontabexample file: [root@blob /etc]# more crontab SHELL=/bin/bash