aboutsummaryrefslogtreecommitdiffstats
path: root/manual/signal.texi
diff options
context:
space:
mode:
authorUlrich Drepper <drepper@redhat.com>2000-03-22 00:10:30 +0000
committerUlrich Drepper <drepper@redhat.com>2000-03-22 00:10:30 +0000
commitbafb8ee92fbb5937357d53b8b9275c99e9da1cfe (patch)
tree795ef9a98481efeb34a23ce3824e629f8fa48342 /manual/signal.texi
parentfd091d3f3464d5e3c625ce89c83b4dd635aea678 (diff)
downloadtermbaud-bafb8ee92fbb5937357d53b8b9275c99e9da1cfe.tar.gz
termbaud-bafb8ee92fbb5937357d53b8b9275c99e9da1cfe.tar.xz
termbaud-bafb8ee92fbb5937357d53b8b9275c99e9da1cfe.zip
Update.
* manual/charset.texi: Fix typos. Rephrase. * manual/process.texi: Likewise. * manual/signal.texi: Likewise. Patches by Mike Coleman <mkc@kc.net>.
Diffstat (limited to 'manual/signal.texi')
-rw-r--r--manual/signal.texi16
1 files changed, 8 insertions, 8 deletions
diff --git a/manual/signal.texi b/manual/signal.texi
index 000bcb90699..95e7a363c0a 100644
--- a/manual/signal.texi
+++ b/manual/signal.texi
@@ -187,7 +187,7 @@ When a signal terminates a process, its parent process can determine the
cause of termination by examining the termination status code reported
by the @code{wait} or @code{waitpid} functions. (This is discussed in
more detail in @ref{Process Completion}.) The information it can get
-includes the fact that termination was due to a signal, and the kind of
+includes the fact that termination was due to a signal and the kind of
signal involved. If a program you run from a shell is terminated by a
signal, the shell typically prints some kind of error message.
@@ -1040,15 +1040,15 @@ a handler for @code{SIGKILL} or @code{SIGSTOP}.
@end table
@end deftypefun
-@strong{Compatibility Note:} A problem when working with the
-@code{signal} function is that it has a different semantic on BSD and
-SVID system. The difference is that on SVID systems the signal handler
-is deinstalled after an signal was delivered. On BSD systems the
+@strong{Compatibility Note:} A problem encountered when working with the
+@code{signal} function is that it has different semantics on BSD and
+SVID systems. The difference is that on SVID systems the signal handler
+is deinstalled after signal delivery. On BSD systems the
handler must be explicitly deinstalled. In the GNU C Library we use the
BSD version by default. To use the SVID version you can either use the
function @code{sysv_signal} (see below) or use the @code{_XOPEN_SOURCE}
-feature select macro (@pxref{Feature Test Macros}). Generally it should
-be avoided to use this functions due to the compatibility problems. It
+feature select macro (@pxref{Feature Test Macros}). In general, use of these
+functions should be avoided because of compatibility problems. It
is better to use @code{sigaction} if it is available since the results
are much more reliable.
@@ -1082,7 +1082,7 @@ main (void)
@end smallexample
@noindent
-Note how if a given signal was previously set to be ignored, this code
+Note that if a given signal was previously set to be ignored, this code
avoids altering that setting. This is because non-job-control shells
often ignore certain signals when starting children, and it is important
for the children to respect this.