finish spellchecking of the signals file

Author: Vladimir Kotal

network.tex

@@ -198,7 +198,7 @@
     transmits datagram
     \end{itemize}
 \item \emph{protocol}: \texttt{0} (default for a given \emph{type})
-or a valid protocol number (eg. \texttt{6}~=~TCP, \texttt{17}~=~UDP)
+or a valid protocol number (e.g. \texttt{6}~=~TCP, \texttt{17}~=~UDP)
 \end{itemize}
 \end{slide}
 
@@ -207,15 +207,15 @@
 \begin{itemize}
 \item Function is declared in \texttt{<sys/socket.h>} as well as other network
 related functions from the previous slide.
-\item Sockets use the same name space as file descriptors, ie. the same
+\item Sockets use the same name space as file descriptors, i.e. the same
 descriptor table.  If you write a simple program that only calls
 \funnm{socket}(), it will return 3 as that will be the first available slot in
 the descriptor table.
 \item Connection-oriented communication is always bidirectional and is similar
 to pipes.  However, note that pipes may not be bidirectional, see page
 \pageref{TWO_WAY_PIPES}.
 \item Sometimes you can see constants beginning with \verb#PF_# (meaning
-\emph{protocol family}, eg. \texttt{PF\_IN\-ET}, \verb#PF_UNIX#, or
+\emph{protocol family}, e.g. \texttt{PF\_IN\-ET}, \verb#PF_UNIX#, or
 \texttt{PF\_IN\-ET6}) and used in a \funnm{socket}() call. Constants \verb#AF_#
 (\emph{address family}) are then used only for naming the sockets.  While it
 might make a better sense, the UNIX specification only defines \verb#AF_#
@@ -295,8 +295,8 @@
 ports and the primary IP address on the interface through which the destination
 can be accessed.  In general, as a client, you do not need a specific outgoing
 port so \funnm{bind}() is usually not needed and the call is typically used only
-by servers as they need a specific port number to be contacted (eg. 443 for
-HTTPS).  Note that some legacy services though, eg. \texttt{rsh}, require the
+by servers as they need a specific port number to be contacted (e.g. 443 for
+HTTPS).  Note that some legacy services though, e.g. \texttt{rsh}, require the
 client to connect from a privileged port (0-1023).  Such a client must call
 \funnm{bind}() to use such a port and also have enough privileges to do that.
 \item \emsl{The address and port must always use network byte ordering.} See
@@ -435,16 +435,16 @@
 \item The newly created socket has the same characteristics as \emph{socket}.
 For example, if \emph{socket} was non-blocking, the new socket is non-blocking
 as well.
-\item If more clients running on the same host connect to the same server (ie.
+\item If more clients running on the same host connect to the same server (i.e.
 using the same IP address and port), individual connections are distinguished
 only by the client side port number.  Do remember that a TCP connection is
-uniquely identified by two sockets, ie. ``((addr1, port1), (addr2, port2)).''
+uniquely identified by two sockets, i.e. ``((addr1, port1), (addr2, port2)).''
 \item The \emph{address} may be \texttt{NULL} which means the caller is not
 interested in the remote end address.  In that case, \emph{address\_len} should
 be \texttt{NULL} as well.
 \item If the code is written to be independent of an address family, it should
 use \texttt{struct sockaddr\_storage} for \emph{address}.  Any specific address
-struct is guaranteed to fit in \texttt{struct sockaddr\_storage}, ie. either
+struct is guaranteed to fit in \texttt{struct sockaddr\_storage}, i.e. either
 \texttt{struct sockaddr\_in} or \texttt{struct sockaddr\_in6}.  Also see page
 \pageref{TCPCLNTEXAMPLE}.
 \item \label{TCP_SINK_SERVER_C} Example: \example{tcp/tcp-sink-server.c}
@@ -588,7 +588,7 @@
     \item \texttt{MSG\_OOB} \dots{} reads urgent (out-of-band)
     data 
     \item \texttt{MSG\_WAITALL} \dots{} waits for the buffer to fill up
-    ie. \emph{l{}en} bytes
+    i.e. \emph{l{}en} bytes
     \end{itemize}
 \end{itemize}
 \end{slide}

signals.tex

@@ -17,10 +17,10 @@
 \item signal categories:
     \begin{itemize}
     \item \emsl{asynchronous events} happening independently of the main program
-    flow, eg. a signal sent from another process, a timer expiration
+    flow, e.g. a signal sent from another process, a timer expiration
     (\texttt{SIGALRM}), terminal disconnect (\texttt{SIGHUP}), or pressing
     \texttt{Ctrl-C} (\texttt{SIGINT})
-    \item \emsl{exceptions} caused by a running process, eg.
+    \item \emsl{exceptions} caused by a running process, e.g.
     attempt to access a restricted area of memory (\texttt{SIGSEGV})
     \end{itemize}
 \end{itemize}
@@ -64,7 +64,7 @@
 \begin{slide}
 \sltitle{Introduction to signals (continued)}
 \begin{itemize}
-\item it is the simplest interprocess communication -- it only carries
+\item it is the simplest inter process communication -- it only carries
 information that an event happened
 \begin{itemize}
 \item there is a real-time POSIX extension that allows for more information,
@@ -92,12 +92,14 @@
 
 \begin{slide}
 \sltitle{Sending signals}
+ifdef([[[NOSPELLCHECK]]], [[[
 \texttt{int \funnm{kill}(pid\_t \emph{pid}, int \emph{sig});}
+]]])
 \begin{itemize}
-\item sends signal \emph{sig} to a process or a process group
-based on value of \emph{pid}: 
+\item sends signal \emph{\texttt{sig}} to a process or a process group
+based on value of \emph{\texttt{pid}}: 
     \begin{itemize}
-    \item \texttt{> 0} \dots{} to process with \emph{pid}
+    \item \texttt{> 0} \dots{} to process with \emph{\texttt{pid}}
     \item \texttt{== 0} \dots{} to all processes in the same group
     \item \texttt{== -1} \dots{} to all aside from system processes
     \item \texttt{< -1} \dots{} to processes in a group \texttt{abs(pid)} 
@@ -148,13 +150,13 @@
 \end{itemize}
 
 Signals \texttt{SIGKILL} and \texttt{SIGSTOP} \emsl{always} trigger an implicit
-action, ie. exit or stop, respectively.
+action, i.e. exit or stop, respectively.
 \end{slide}
 
 \begin{itemize}
 \item Creating a core dump means to store the contents of the process virtual
 address space to a file.  Usually such file has a word \texttt{core} in its
-filename.  Some systems, eg. macOS, may not generate core dumps by default even
+filename.  Some systems, e.g. macOS, may not generate core dumps by default even
 if its for signals with default core dump action.
 \item Most of the signals implicitly terminate the process, some create a core
 dump on top of that to enable a post-mortem analysis.
@@ -185,7 +187,7 @@
 \emsl{Detected errors:}
 
 \begin{tabular}{ll}
-\texttt{SIGBUS} & bus error, eg. wrong alignment (core) \\
+\texttt{SIGBUS} & bus error, e.g. wrong alignment (core) \\
 \texttt{SIGFPE} & floating point exception (core) \\
 \texttt{SIGILL} & illegal instructions (core) \\
 \texttt{SIGSEGV} & segmentation violation (core) \\
@@ -231,7 +233,7 @@
 \item If such a signal is masked while the signal is being delivered, the
 program behavior is undefined.
 \end{itemize}
-\item Bottom line is that if a hardware generated error is real (ie. the signal
+\item Bottom line is that if a hardware generated error is real (i.e. the signal
 is not send via \funnm{kill} or similar functions), the process may never get
 over that error at all.  It is not safe to ignore such errors, continue after
 returning from a handler, or mask such signals.  You can catch such signals
@@ -275,8 +277,8 @@
 know what you are doing.  For example, if a running process does not respond to
 user input nor any other signal.  Many applications, mainly daemons, rely on the
 fact that they are sent \texttt{SIGTERM} on termination, which they often handle
-and perform pre-exit actions.  For example, flushing the database, removing
-temporary files and file locks, etc.  So, do not use \texttt{SIGKILL} right away
+and perform actions before exit. For example, flushing the database, removing
+temporary files and file locks, etc. So, do not use \texttt{SIGKILL} right away
 only because "it's the simplest way to kill a process" as you might run in
 trouble.
 \item Example on using \texttt{SIGQUIT} on Solaris:
@@ -356,36 +358,44 @@
 
 %%%%%
 
+ifdef([[[NOSPELLCHECK]]], [[[
 \pdfbookmark[1]{sigaction}{sigaction}
+]]])
 
 \begin{slide}
 \sltitle{Setting actions for signals}
+ifdef([[[NOSPELLCHECK]]], [[[
 \begin{minipage}{\slidewidth}\vspace{-1\baselineskip}\texttt{\begin{tabbing}
 int \funnm{sigaction}(\=int \emph{sig},
 const struct sigaction *\emph{act},\\\> struct sigaction *\emph{oact});
+]]])
 \end{tabbing}}
 \end{minipage}
 \begin{itemize}
-\item assigns an action \emph{act} for a signal \emph{sig},
-previous setting is returned in \emph{oact}, if non-zero
+\item assigns an action \emph{\texttt{act}} for a signal \emph{\texttt{sig}},
+previous setting is returned in \emph{\texttt{oact}}, if non-zero
 \item structure \texttt{sigaction} contains:
     \begin{itemize}
+ifdef([[[NOSPELLCHECK]]], [[[
     \item \texttt{void (*\emph{sa\_handler})(int)} \dots{} \texttt{SIG\_DFL},
-    \texttt{SIG\_IGN}, or a handler address (ie. a handler function name)
-    \item \texttt{sigset\_t \emph{sa\_mask}} \dots{} signals blocked while in
-    handler; plus \emph{sig} is blocked by default
-    \item \texttt{int \emph{sa\_flags}} \dots{} \texttt{SA\_RESETHAND} (handler
+]]])
+    \texttt{SIG\_IGN}, or a handler address (i.e. a handler function name)
+    \item ifdef([[[NOSPELLCHECK]]], [[[\texttt{sigset\_t \emph{sa\_mask}}]]])
+     \dots{} signals blocked while in
+    handler; plus \emph{\texttt{sig}} is blocked by default
+    \item ifdef([[[NOSPELLCHECK]]], [[[\texttt{int \emph{sa\_flags}}]]])
+     \dots{} \texttt{SA\_RESETHAND} (handler
     is reset to \texttt{SIG\_DFL} at the moment the signal is delivered),
     \texttt{SA\_RESTART} (restart pending calls), \texttt{SA\_NODEFER}
-    (do not block \emph{sig} while in handler)
+    (do not block \emph{\texttt{sig}} while in handler)
     \end{itemize}
 \end{itemize}
 \end{slide}
 
 \begin{itemize}
 \item If \texttt{act == NULL} you only get the present setting and nothing is
 changed.  If not interested in previous setting, use \texttt{NULL} for
-\emph{oact}.
+\emph{\texttt{oact}}.
 \item If \texttt{SA\_RESTART} is not set, the system call interrupted by the
 signal will return an error with \texttt{errno} set to \texttt{EINTR} (some
 calls actually return directly the \texttt{errno} value but that is not relevant
@@ -400,7 +410,8 @@
 to make sure the signal is not delivered in the wrong time (for example, the
 signal is delivered within a function and the same function is called from the
 handler, and the function is not ready for that).  Minimal set of functions
-that must be \emsl{\emph{async-signal-safe}} is listed in SUSv4 in section
+that must be ifdef([[[NOSPELLCHECK]]], [[[\emsl{\emph{async-signal-safe}}]]])
+is listed in SUSv4 in section
 \emph{System Interfaces: General Information $\Rightarrow$ Signal Concepts
 $\Rightarrow$ Signal Actions (2.4.3)}.  Systems can extend the list, of course.
 Whether a function is safe to use in a signal handler or not should be
@@ -485,16 +496,20 @@
 
 %%%%%
 
+ifdef([[[NOSPELLCHECK]]], [[[
 \pdfbookmark[1]{sigprocmask, sigpending}{sigblock}
+]]])
 
 \begin{slide}
 \sltitle{Signal blocking}
 \begin{itemize}
 \item blocked signals are delivered to the process after getting unblocked again
 \end{itemize}
 \begin{minipage}{\slidewidth}\texttt{\begin{tabbing}
+ifdef([[[NOSPELLCHECK]]], [[[
 int \funnm{sigprocmask}(\=int \emph{how}, const sigset\_t *\emph{set},\\
 \>sigset\_t *\emph{oset});
+]]])
 \end{tabbing}}
 \end{minipage}
 \begin{itemize}
@@ -506,7 +521,9 @@
 \funnm{sigdelset}(), \funnm{sigemptyset}(), \funnm{sigfillset}(),
 \funnm{sigismember}()
 \end{itemize}
+ifdef([[[NOSPELLCHECK]]], [[[
 \texttt{int \funnm{sigpending}(sigset\_t *\emph{set});}
+]]])
 \begin{itemize}
 \item returns a mask for the signals pending for delivery
 \end{itemize}
@@ -526,8 +543,9 @@
 \pageref{REALTIMEEXTENSIONS} and the use of \texttt{SA\_SIGINFO}), signals are
 delivered through a queue and multiple signals are never squeezed into one
 delivery.
-\item Both arguments \emph{oset} and \emph{set} may be \texttt{NULL}.  If both
-are \texttt{NULL} in the same invocation of the function, nothing happens.
+\item Both arguments \emph{\texttt{oset}} and \emph{set} may be \texttt{NULL}.
+If both are \texttt{NULL} in the same invocation of the function, nothing
+happens.
 \end{itemize}
 
 %%%%%
@@ -570,7 +588,9 @@
 %%%%%
 
 \label{SIGWAIT}
+ifdef([[[NOSPELLCHECK]]], [[[
 \pdfbookmark[1]{pause, sigsuspend, sigwait}{sigwait}
+]]])
 
 \begin{slide}
 \sltitle{Waiting for a signal}
@@ -579,14 +599,18 @@
 \item suspends the caller until delivery of a signal that is not blocked or
 ignored
 \end{itemize}
+ifdef([[[NOSPELLCHECK]]], [[[
 \texttt{int \funnm{sigsuspend}(const sigset\_t *\emph{sigmask});}
+]]])
 \begin{itemize}
 \item like \funnm{pause}(), also temporarily changes the blocked signal mask
 \end{itemize}
+ifdef([[[NOSPELLCHECK]]], [[[
 \texttt{int \funnm{sigwait}(const sigset\_t *\emph{set}, int *\emph{sig});}
+]]])
 \begin{itemize}
 \item waits for a signal from \emph{set} (must be blocked) and puts the signal
-number to \emph{sig}.
+number to \emph{\texttt{sig}}.
 \item the signal handler is not called
 \end{itemize}
 \end{slide}

threads.tex

@@ -114,10 +114,10 @@
 \item so you cannot use functions \funnm{perror}() or \funnm{err}()
 \end{itemize}
 \item the standard also defines other functions, for example those that could
-not be possible to adjust for the use with threads without changing its API (eg.
+not be possible to adjust for the use with threads without changing its API (e.g.
 \texttt{readdir\_r}, \texttt{strtok\_r}, etc.)
 \begin{itemize}
-\item \texttt{\_r} means \emph{reentrant}, ie. the function can be called by
+\item \texttt{\_r} means \emph{reentrant}, i.e. the function can be called by
 multiple threads without any side effects
 \end{itemize}
 \end{itemize}
@@ -209,7 +209,7 @@
 \\\>void *(*\emph{start\_fn})(void*), void *\emph{arg});}
 \begin{itemize}
 \item creates a new thread, puts its ID to \emph{thread}
-\item with attributes from \texttt{attr}, eg. its stack size,
+\item with attributes from \texttt{attr}, e.g. its stack size,
 \texttt{NULL} means default attributes
 \item function \emph{start\_fn}() will be started in the thread using argument
 \emph{arg}.  After the function returns, the thread ceases to exist.
@@ -257,7 +257,7 @@
 to map to the native threads provided by the system.  If you create several
 threads, you need to pass a different address for a \texttt{pthread\_t} variable
 otherwise you will not be able to further manipulate with the threads from the
-main thread, eg. waiting for them to finish.
+main thread, e.g. waiting for them to finish.
 \end{itemize}
 
 %%%%%
@@ -350,7 +350,7 @@
 \item In contrast to waiting for processes to finish, \emsl{one cannot wait for
 any thread to finish}.  The rationale is that since there is not parent--child
 relation, it was not deemed necessary.  However, some system provide that
-functionality, eg.  on Solaris you can use \texttt{0} for a thread ID in
+functionality, e.g.  on Solaris you can use \texttt{0} for a thread ID in
 \funnm{thr\_join}().  If you needed this functionality with POSIX thread API, it
 is easy to set threads as \emph{detached} and use a condition variable together
 with a global variable.  More on that on page \pageref{CONDITION_VARIABLES}.
@@ -546,7 +546,7 @@
 \item No cleanup routines or thread specific data destructors are called for
 threads not propagated to the new process.
 \item \label{FORKALL} Note that the way how \funnm{fork}() works also depends on
-the system used.  For example, in Solaris before version 10 (ie. before 2005),
+the system used.  For example, in Solaris before version 10 (i.e. before 2005),
 \funnm{fork}() in the \texttt{libthread} library (different from
 \texttt{libpthread}) was the same as \funnm{forkall}().
 \item Examples: \example{pthreads/fork.c},

unix_dict.txt

@@ -1,4 +1,4 @@
-personal_ws-1.1 en 333 
+personal_ws-1.1 en 338 
 Illumos
 Prog
 Ctrl
@@ -31,6 +31,7 @@ Kernighan
 reentrant
 userland
 TLI
+RTS
 args
 FIFO
 argv
@@ -53,6 +54,7 @@ SunOS
 Gdb
 gdb
 FFS
+interruptible
 verlagen
 EOB
 programmatically
@@ -204,6 +206,7 @@ Pechanec
 ld
 jp
 LF
+mortem
 http
 li
 HURD
@@ -315,11 +318,13 @@ CSRG
 symlink's
 symlinks
 OpenBSD
+signalling
 SCO
 Xcurses
 microkernel
 GETFD
 virtualized
+multithreaded
 changequote
 decrement
 PWB