Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: kill(2)
- To: tlug@example.com
- Subject: Re: kill(2)
- From: SL Baur <steve@example.com>
- Date: 28 Jun 2001 13:31:08 +0900
- Content-Type: text/plain; charset=US-ASCII
- In-Reply-To: vp@example.com's message of "28 Jun 2001 12:03:18 +0900"
- Mail-Copies-To: never
- References: <3B3A9E76.40430.001@example.com>
- Reply-To: tlug@example.com
- Resent-From: tlug@example.com
- Resent-Message-ID: <9Oo9zC.A.TiF.nJrO7@example.com>
- Resent-Sender: tlug-request@example.com
Viktor Pavlenko <vp@example.com> writes in tlug@example.com: > Here is an excerpt from HP's kill(2) man page (the one on linux > is too sparse): > The real or effective user ID of the sending process must match the > real or saved user ID of the receiving process unless the effective > user ID of the sending process is a user who has appropriate > privileges. > Can anybody tell me what's exactly `appropriate privileges'? POSIX capabilities? The Linux kernel source documents CAP_KILL as: /* Overrides the restriction that the real or effective user ID of a process sending a signal must match the real or effective user ID of the process receiving the signal. */ You are much better off reading source than HP/UX kernel man pages.
- References:
- kill(2)
- From: vp@example.com (Viktor Pavlenko)
Home | Main Index | Thread Index
- Prev by Date: Re: Q.
- Next by Date: Re: kill(2)
- Prev by thread: kill(2)
- Next by thread: Re: kill(2)
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links