Typo in man-page: SIGNAL(7)

Typo in man-page: SIGNAL(7)

[Pablo M. Ronchi]

In the URL:

http://man7.org/linux/man-pages/man7/signal.7.html

there is the following duplication typo at the end of the paragraph: "it 
was it was" (marked in capital letters, below)

...
Signal mask and pending signals
...
A signal may be blocked, which means that it will not be delivered until 
it is later unblocked. Between the time when it is generated and when it 
is delivered a signal is said to be pending. Each thread in a process 
has an independent signal mask, which indicates the set of signals that 
the thread is currently blocking. A thread can manipulate its signal 
mask using pthread_sigmask(3). In a traditional single-threaded 
application, sigprocmask(2) can be used to manipulate the signal mask. A 
child created via fork(2) inherits a copy of its parent's signal mask; 
the signal mask is preserved across execve(2). A signal may be 
process-directed or thread-directed. A process- directed signal is one 
that is targeted at (and thus pending for) the process as a whole. A 
signal may be process-directed because it was generated by the kernel 
for reasons other than a hardware exception, or because it was sent 
using kill(2) or sigqueue(3). A thread- directed signal is one that is 
targeted at a specific thread. A signal may be thread-directed because 
it was generated as a consequence of executing a specific 
machine-language instruction that triggered a hardware exception (e.g., 
SIGSEGV for an invalid memory access, or SIGFPE for a math error), or 
because IT WAS IT WAS targeted at a specific thread using interfaces 
such as tgkill(2) or pthread_kill(3).
...


Thanks for the great work.

Pablo M. Ronchi

Re: Typo in man-page: SIGNAL(7)

[Michael Kerrisk (man-pages)]

On 3/26/20 6:17 PM, Pablo M. Ronchi wrote:
> In the URL:
> 
> http://man7.org/linux/man-pages/man7/signal.7.html
> 
> there is the following duplication typo at the end of the paragraph: "it 
> was it was" (marked in capital letters, below)
> 
> ...
> Signal mask and pending signals
> ...
> A signal may be blocked, which means that it will not be delivered until 
> it is later unblocked. Between the time when it is generated and when it 
> is delivered a signal is said to be pending. Each thread in a process 
> has an independent signal mask, which indicates the set of signals that 
> the thread is currently blocking. A thread can manipulate its signal 
> mask using pthread_sigmask(3). In a traditional single-threaded 
> application, sigprocmask(2) can be used to manipulate the signal mask. A 
> child created via fork(2) inherits a copy of its parent's signal mask; 
> the signal mask is preserved across execve(2). A signal may be 
> process-directed or thread-directed. A process- directed signal is one 
> that is targeted at (and thus pending for) the process as a whole. A 
> signal may be process-directed because it was generated by the kernel 
> for reasons other than a hardware exception, or because it was sent 
> using kill(2) or sigqueue(3). A thread- directed signal is one that is 
> targeted at a specific thread. A signal may be thread-directed because 
> it was generated as a consequence of executing a specific 
> machine-language instruction that triggered a hardware exception (e.g., 
> SIGSEGV for an invalid memory access, or SIGFPE for a math error), or 
> because IT WAS IT WAS targeted at a specific thread using interfaces 
> such as tgkill(2) or pthread_kill(3).
> ...

Thanks, Pablo. Fixed!

Cheers,

Michael

-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/