linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Jakub Wilk <jwilk@jwilk.net>
Cc: Helge Kreutzmann <debian@helgefjell.de>,
	linux-man <linux-man@vger.kernel.org>
Subject: Re: Errors in man pages, here: signal(7): Sentence to long
Date: Mon, 20 Apr 2020 10:51:00 +0200	[thread overview]
Message-ID: <CAKgNAkj6j2Y1YphseM54y_2=xQV3E4Rc+UX4TPC4VgtX4D0V9w@mail.gmail.com> (raw)
In-Reply-To: <20200420084932.xvz32vuv7uqudyih@jwilk.net>

On Mon, 20 Apr 2020 at 10:49, Jakub Wilk <jwilk@jwilk.net> wrote:
>
> * Michael Kerrisk (man-pages) <mtk.manpages@gmail.com>, 2020-04-20, 10:33:
> >>"A signal may be generated (and thus pending)  for a process as a whole (e."
> >>"g., when sent using B<kill>(2))  or for a specific thread (e.g., certain "
> >>"signals, such as B<SIGSEGV> and B<SIGFPE>, generated as a consequence of "
> >>"executing a specific machine-language instruction are thread directed, as "
> >>"are signals targeted at a specific thread using B<pthread_kill>(3)).  A "
> >>"process-directed signal may be delivered to any one of the threads that does "
> >>"not currently have the signal blocked.  If more than one of the threads has "
> >>"the signal unblocked, then the kernel chooses an arbitrary thread to which "
> >>"to deliver the signal."
> >
> >I can't find the text referred to. I think you may be working
> >with an older version of the page. Can you please check.
>
> In 3b9d44099f234e8e, the long sentence was replaced with this paragraph:
>
> "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 signals 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, Jakub.


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

  reply	other threads:[~2020-04-20  8:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-19  6:48 Errors in man pages, here: signal(7): Sentence to long Helge Kreutzmann
2020-04-20  8:33 ` Michael Kerrisk (man-pages)
2020-04-20  8:49   ` Jakub Wilk
2020-04-20  8:51     ` Michael Kerrisk (man-pages) [this message]
2020-04-24 18:50       ` Helge Kreutzmann

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='CAKgNAkj6j2Y1YphseM54y_2=xQV3E4Rc+UX4TPC4VgtX4D0V9w@mail.gmail.com' \
    --to=mtk.manpages@gmail.com \
    --cc=debian@helgefjell.de \
    --cc=jwilk@jwilk.net \
    --cc=linux-man@vger.kernel.org \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).