Linux-man Archive on lore.kernel.org
 help / color / Atom feed
From: "Pablo M. Ronchi" <pmronchi@yahoo.com.ar>
To: mtk.manpages@gmail.com
Cc: linux-man@vger.kernel.org
Subject: Typo in man-page: SIGNAL(7)
Date: Thu, 26 Mar 2020 14:17:07 -0300
Message-ID: <fa469dfc-71ce-e7a2-dd83-b9566cc7ba58@yahoo.com.ar> (raw)
In-Reply-To: <fa469dfc-71ce-e7a2-dd83-b9566cc7ba58.ref@yahoo.com.ar>

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


       reply index

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa469dfc-71ce-e7a2-dd83-b9566cc7ba58.ref@yahoo.com.ar>
2020-03-26 17:17 ` Pablo M. Ronchi [this message]
2020-03-29  7:23   ` Michael Kerrisk (man-pages)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fa469dfc-71ce-e7a2-dd83-b9566cc7ba58@yahoo.com.ar \
    --to=pmronchi@yahoo.com.ar \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-man Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-man/0 linux-man/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-man linux-man/ https://lore.kernel.org/linux-man \
		linux-man@vger.kernel.org
	public-inbox-index linux-man

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-man


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git