diff options
| author | John Ogness <john.ogness@linutronix.de> | 2019-01-18 15:23:06 +0100 |
|---|---|---|
| committer | John Ogness <john.ogness@linutronix.de> | 2019-01-18 15:23:06 +0100 |
| commit | 07d65b50c4156453099a3a2083804e00451e2041 (patch) | |
| tree | b834e747740fd54c324f428137cb3d1f7f93f07a | |
| parent | 168c38234b184f4b600db64f77af0749fde33c10 (diff) | |
pres_signals: fix typos
Signed-of-by: Holger Dengler <dengler@linutronix.de>
Signed-off-by: John Ogness <john.ogness@linutronix.de>
| -rw-r--r-- | application-devel/signals/pres_signals_en.tex | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/application-devel/signals/pres_signals_en.tex b/application-devel/signals/pres_signals_en.tex index 6540b3b..9111298 100644 --- a/application-devel/signals/pres_signals_en.tex +++ b/application-devel/signals/pres_signals_en.tex @@ -59,7 +59,7 @@ Three possibilities are available how a signal can be disposed: \begin{frame} \frametitle{special signals} -Two signals cannot be caught: +Two signals can not be caught: \begin{itemize} \item SIGKILL \item SIGSTOP @@ -115,7 +115,7 @@ run our small example ^Creceived SIGINT ^Creceived SIGINT \end{lstlisting} -We tried the key combination ctrl+c several times but each time the process didn’t terminate. This is because the signal was handled in the code and this was confirmed from the print we got on each line. +We tried the key combination ctrl+c several times but each time the process didn't terminate. This is because the signal was handled in the code and this was confirmed from the print we got on each line. \end{frame} \begin{frame} @@ -129,8 +129,8 @@ Two possibilities for sending a signal: \subsubsection{Pitfalls} \begin{frame} -\frametitle{signal handler must be reentrant} -Reentrant means: The function can be stopped in between due to any reason (like due to interrupt or signal) and then can be reentered again safely before its previous invocations complete the execution. +\frametitle{signal handler must be re-entrant} +Re-entrant means: The function can be stopped in between due to any reason (like due to interrupt or signal) and then can be reentered again safely before its previous invocations complete the execution. \bigskip Reason: Signals are asynchronous events. It could be possible the signal occurs again before the signal handler is still called. @@ -160,7 +160,7 @@ This mean: it is not clear from which thread the signal handler is called! \subsubsection{Alternative} \begin{frame} \frametitle{Signals should not be used} -Use other mechanismen like: +Use other mechanisms like: \begin{itemize} \item files \item pipes |