linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r@public.gmane.org
To: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [Bug 71061] New: msgctl(2) manpage : put back a condition of EPERM error code forgotten
Date: Mon, 24 Feb 2014 08:02:17 +0000	[thread overview]
Message-ID: <bug-71061-11311@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 71061
           Summary: msgctl(2) manpage : put back a condition of EPERM
                    error code forgotten
           Product: Documentation
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P1
         Component: man-pages
          Assignee: documentation_man-pages-ztI5WcYan/vQLgFONoPN62D2FQJk+8+b@public.gmane.org
          Reporter: fboiteux-N+jn5RlININWk0Htik3J/w@public.gmane.org
        Regression: No

Hello,

  I've noticed in the msgctl(2) manpage that a condition to get an EPERM error
code was dropped in the past : it's about trying to modify the size of a
message queue (msg_qbytes) larger than the max size set in kernel (look at
/proc/sys/kernel/msgmnb).

In a (very old) manpage of a Debian Woody 3.0 (!), we could read :

       EPERM      The argument cmd has value IPC_SET or IPC_RMID but the
calling process effective user-ID has insufficient privileges to
                  execute  the  command.   Note this is also the case of a non
super-user process trying to increase the msg_qbytes value
                  beyond the value specified by the system parameter MSGMNB.


thereas on later pages (on my Debian Wheezy 7.4, but also in current version of
kernel manpages), we only have :

       EPERM  The argument cmd has the value IPC_SET or IPC_RMID, but the
effective user ID of the calling process is not the creator  (as  found  in
              msg_perm.cuid) or the owner (as found in msg_perm.uid) of the
message queue, and the process is not privileged (Linux: it does not have
              the CAP_SYS_ADMIN capability).


Could you put back in the man page a sentence like : 'Note this is also the
case of a non super-user process trying to increase the msg_qbytes value
                  beyond the value specified by the system parameter MSGMNB.'


      Thanks,
            Frédéric.

-- 
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

             reply	other threads:[~2014-02-24  8:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-24  8:02 bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r [this message]
     [not found] ` <bug-71061-11311-3bo0kxnWaOQUvHkbgXJLS5sdmw4N0Rt+2LY78lusg7I@public.gmane.org/>
2014-02-24  8:03   ` [Bug 71061] msgctl(2) manpage : put back a condition of EPERM error code forgotten bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r
2014-02-24  8:52   ` bugzilla-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r

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-71061-11311@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 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).