public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Jochen Roemling <jochen@roemling.net>
Cc: linux-kernel@vger.kernel.org, Chris Wright <chrisw@osdl.org>
Subject: Re: shmget with SHM_HUGETLB flag: Operation not permitted
Date: Thu, 26 Feb 2004 16:58:27 -0800	[thread overview]
Message-ID: <20040227005827.GS693@holomorphy.com> (raw)
In-Reply-To: <403E90DD.9060005@roemling.net>

On Fri, Feb 27, 2004 at 01:35:41AM +0100, Jochen Roemling wrote:
> Ok. One step further now. The syntax seems correct now. I tried to grant 
> capabilities to the user's shell:
> roesrv01~ # setpcaps cap_ipc_lock+e 2864
> [caps set to:
> = cap_ipc_lock+e
> ]
> Failed to set cap's on process `2864': (Operation not permitted)
> and with the setcap tool again:

This is likely due to not having the capability to grant in the granting
process. Things are supposed to be vauely montonic here.

On Fri, Feb 27, 2004 at 01:35:41AM +0100, Jochen Roemling wrote:
> roesrv01~ # setcap cap_ipc_lock+e a.out
> Failed to set capabilities on file `a.out'
>  (Function not implemented)
> Hmmm. What do we do now?

setcap on executables probably isn't supported by your fs.


-- wli

  reply	other threads:[~2004-02-27  1:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1tDJX-4Ua-25@gated-at.bofh.it>
     [not found] ` <1tDJX-4Ua-27@gated-at.bofh.it>
     [not found]   ` <1tDJX-4Ua-29@gated-at.bofh.it>
     [not found]     ` <1tDTE-51P-23@gated-at.bofh.it>
     [not found]       ` <1tDTE-51P-21@gated-at.bofh.it>
2004-02-27  0:35         ` shmget with SHM_HUGETLB flag: Operation not permitted Jochen Roemling
2004-02-27  0:58           ` William Lee Irwin III [this message]
     [not found] <1tCuq-3AH-1@gated-at.bofh.it>
     [not found] ` <1tCEo-3Lh-27@gated-at.bofh.it>
     [not found]   ` <1tDgT-4r2-13@gated-at.bofh.it>
2004-02-27  0:02     ` Jochen Roemling
     [not found]     ` <403E87CF.1080409@roemling.net>
2004-02-27  0:06       ` Chris Wright
2004-02-27  0:32         ` Chris Wright
2004-02-27  0:55           ` Jochen Roemling
2004-02-27  1:11             ` William Lee Irwin III
2004-02-27  1:33               ` Jochen Roemling
2004-02-27  2:11                 ` William Lee Irwin III
2004-02-29 21:37                   ` Jochen Roemling
2004-02-29 22:31                     ` William Lee Irwin III
2004-02-27 16:32                 ` Zlatko Calusic
2004-02-27 16:35                   ` William Lee Irwin III
2004-02-27 16:42                     ` Zlatko Calusic
2004-02-27  0:42         ` Wim Coekaerts
2004-02-26 22:36 Jochen Roemling
2004-02-26 22:52 ` William Lee Irwin III
2004-02-26 23:27   ` Chris Wright

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=20040227005827.GS693@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=chrisw@osdl.org \
    --cc=jochen@roemling.net \
    --cc=linux-kernel@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