All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r@public.gmane.org
To: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [Bug 134971] Clarify kill(2) man-page for permission to "send" signal 0
Date: Sat, 16 Jul 2016 13:12:15 +0000	[thread overview]
Message-ID: <bug-134971-11311-G7DIxE3MmL@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-134971-11311-3bo0kxnWaOQUvHkbgXJLS5sdmw4N0Rt+2LY78lusg7I@public.gmane.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=134971

--- Comment #2 from John Wiersba <jrw32982-/E1597aS9LQAvxtiuMwx3w@public.gmane.org> ---
Thanks, Michael!  That does make it clearer!



      From: "bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r@public.gmane.org"
<bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r@public.gmane.org>
 To: jrw32982-/E1597aS9LQAvxtiuMwx3w@public.gmane.org 
 Sent: Saturday, July 16, 2016 6:24 AM
 Subject: [Bug 134971] Clarify kill(2) man-page for permission to "send" signal
0

https://bugzilla.kernel.org/show_bug.cgi?id=134971

Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> changed:

          What    |Removed                    |Added
----------------------------------------------------------------------------
            Status|NEW                        |RESOLVED
                CC|                            |mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
        Resolution|---                        |CODE_FIX

--- Comment #1 from Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> ---
Hello John,

I agree the page could be clearer. What I did was change the paragraph
describing sig==0 to:

      If sig is 0, then no signal is sent, but existence and  permission
      checks  are  still  performed;  this  can be used to check for the
      existence of a process ID or process group ID that the  caller  is
      permitted to signal.

I believe that makes the point clear, so I'll close this for now. Please reopen
if you think there's still a problem.

Thanks,

Michael

-- 
You are receiving this mail because:
You are watching the assignee of the bug.--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2016-07-16 13:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-15  2:50 [Bug 134971] New: Clarify kill(2) man-page for permission to "send" signal 0 bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r
     [not found] ` <bug-134971-11311-3bo0kxnWaOQUvHkbgXJLS5sdmw4N0Rt+2LY78lusg7I@public.gmane.org/>
2016-07-16 10:24   ` [Bug 134971] " bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r
2016-07-16 13:12   ` bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r [this message]

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=bug-134971-11311-G7DIxE3MmL@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon-590eeb7gvniway/ihj7yzeb+6bgklq7r@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.