From: Prof Brucee <prof.brucee@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] ps bug
Date: Wed, 12 Apr 2017 13:16:56 +1000 [thread overview]
Message-ID: <CAJDwFdifhSSB47c7U+kHHiOXBrSKxpCvRyDvWPuqazWJfUGnSg@mail.gmail.com> (raw)
In-Reply-To: <CAJDwFdgeiMVxvkTv8y55bP+11wWR4JKjndCem+XGSX7qsQcVyA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1174 bytes --]
Ubuntu doesn't return all processes for "ps -e" so I guess there's
something deeply wrong with /proc.
brucee
On 12/04/2017 12:56 AM, "Mat Kovach" <mek@well.com> wrote:
>From the man page:
=$ man ps
PS(1) PS(1)
NAME
ps, psu - process status
SYNOPSIS
ps [ -pa ]
psu [ -pa ] [ user ]
[snip]
With the -p flag, ps also prints, after the system time, the
baseline and current priorities of each process.
The -a flag causes ps to print the arguments for the pro-
cess. Newlines in arguments will be translated to spaces
for display.
plan9port's ps does not have a '-e' option, if given it is ignore.
Checking the script, ps uses the os version of ps and the arguments -axww
------------------------------
*From: *"Bruce Ellis" <bruce.ellis@gmail.com>
*To: *"Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
*Sent: *Tuesday, April 11, 2017 2:54:07 AM
*Subject: *[9fans] ps bug
using plan9ports' "ps -e" does not print all processes. dirread /proc fun I
guess.
brucee
[-- Attachment #2: Type: text/html, Size: 2031 bytes --]
next prev parent reply other threads:[~2017-04-12 3:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 6:54 Bruce Ellis
2017-04-11 7:21 ` Sergey Zhilkin
2017-04-11 7:34 ` Sergey Zhilkin
2017-04-11 7:51 ` Bruce Ellis
2017-04-11 11:57 ` Sergey Zhilkin
2017-04-11 14:56 ` Mat Kovach
[not found] ` <CAJDwFdiodCrtJr9=146C268u99b3vh=f6xK5yCK_HeYTTpqJCQ@mail.gmail.com>
[not found] ` <CAJDwFdgeiMVxvkTv8y55bP+11wWR4JKjndCem+XGSX7qsQcVyA@mail.gmail.com>
2017-04-12 3:16 ` Prof Brucee [this message]
2017-04-12 3:31 ` Winston Kodogo
[not found] ` <CAJDwFdihshU+WA2p6hE10C5H03CRKen_G5E5zRT6U6a10WdKzQ@mail.gmail.com>
[not found] ` <CAJDwFdi97aQeC-EvFt-fsUkgxF-2JfPWMQV_6ChmRh_74a9+MA@mail.gmail.com>
2017-04-12 4:03 ` Prof Brucee
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=CAJDwFdifhSSB47c7U+kHHiOXBrSKxpCvRyDvWPuqazWJfUGnSg@mail.gmail.com \
--to=prof.brucee@gmail.com \
--cc=9fans@9fans.net \
/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).