From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Privilege(s) needed to run top command
Date: Tue, 12 Mar 2019 08:58:00 -0000 [thread overview]
Message-ID: <20190312085809.GG3785@calimero.vinschen.de> (raw)
In-Reply-To: <87ef7d3x9b.fsf@Rainer.invalid>
[-- Attachment #1: Type: text/plain, Size: 871 bytes --]
On Mar 11 22:40, Achim Gratz wrote:
> Corinna Vinschen writes:
> > (*) That doesn't mean it's not possible. In theory all Cygwin
> > processes could be opened to allow everyone
> > PROCESS_QUERY_LIMITED_INFORMATION access, which would at least
> > fill most of /proc/<PID>/stat for foreign processes.
> > However, we never did that, so it can't have worked yet.
>
> Could we make it work under the condition that cygserver is running?
If this functionality is really necessary, it should ideally work
without having a service running.
Another, easier way out would be to allow /proc/<PID>/stat (and perhaps
others) to succeed even if the process info can't be grabbed due to
permissions. It wouldn't show really useful info, but procps or top
would at least show the process.
Corinna
--
Corinna Vinschen
Cygwin Maintainer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-03-12 8:58 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 16:56 jwang
2019-03-11 20:29 ` L A Walsh
2019-03-11 20:41 ` Achim Gratz
2019-03-11 21:28 ` Corinna Vinschen
2019-03-11 21:40 ` Achim Gratz
2019-03-12 0:20 ` Andrey Repin
2019-03-12 8:58 ` Corinna Vinschen [this message]
2019-03-12 9:48 ` jwang
2019-03-12 11:14 ` Corinna Vinschen
2019-03-12 12:01 ` jwang
2019-03-12 12:39 ` Houder
2019-03-12 15:51 ` jwang
2019-03-12 16:47 ` Corinna Vinschen
2019-03-12 17:06 ` jwang
2019-03-12 17:13 ` Corinna Vinschen
2019-03-12 17:19 ` jwang
2019-03-12 17:40 ` Corinna Vinschen
2019-03-12 17:39 ` Corinna Vinschen
2019-03-12 20:28 ` Corinna Vinschen
2019-03-12 20:50 ` Andrey Repin
2019-03-12 20:59 ` Corinna Vinschen
2019-03-12 21:50 ` Andrey Repin
2019-03-12 18:10 ` Houder
2019-03-12 19:27 ` Achim Gratz
2019-03-13 9:17 ` jwang
2019-03-15 10:20 ` jwang
2019-03-15 11:28 ` Corinna Vinschen
2019-03-15 12:34 ` jwang
2019-03-15 13:38 ` Corinna Vinschen
2019-03-15 13:50 ` jwang
2019-03-15 14:11 ` jwang
2019-03-15 14:53 ` Corinna Vinschen
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=20190312085809.GG3785@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).