public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>, linux-man@vger.kernel.org
Cc: Alejandro Colomar <alx@kernel.org>, Tejun Heo <tj@kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Craig Small <csmall@enc.com.au>,
	Alexey Dobriyan <adobriyan@gmail.com>,
	Michael Kerrisk <mtk.manpages@gmail.com>
Subject: Re: [PATCH 1/2] proc.5: note that "cmdline" might be favored over "stat.comm" by ps(1)
Date: Wed, 28 Dec 2022 21:27:16 +0100	[thread overview]
Message-ID: <6f424f4b-6fa2-488d-74c9-0e66199baa07@gmail.com> (raw)
In-Reply-To: <patch-1.2-90c53495f-20221223T174835Z-avarab@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1565 bytes --]

Hi Ævar,

On 12/23/22 18:59, Ævar Arnfjörð Bjarmason wrote:
> With "ps -A" the output uses the "stat.comm" field, but "ps a" will
> display the value in "cmdline".
> 
> Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
> ---
>   man5/proc.5 | 6 +++++-
>   1 file changed, 5 insertions(+), 1 deletion(-)
> 
> diff --git a/man5/proc.5 b/man5/proc.5
> index 65a4c38e3..115c8592e 100644
> --- a/man5/proc.5
> +++ b/man5/proc.5
> @@ -2087,7 +2087,11 @@ The affected fields are indicated with the marking [PT].
>   The process ID.
>   .TP
>   (2) \fIcomm\fP \ %s
> -The filename of the executable, in parentheses.
> +The filename of the executable, in parentheses. Tools such as

Please use semantic newlines.  See man-pages(7):

    Use semantic newlines
        In  the source of a manual page, new sentences should be started on new
        lines, long sentences should be split into lines at clause breaks (com‐
        mas, semicolons, colons, and so on), and long clauses should  be  split
        at  phrase  boundaries.   This convention, sometimes known as "semantic
        newlines", makes it easier to see the effect of  patches,  which  often
        operate at the level of individual sentences, clauses, or phrases.


Cheers,

Alex

> +.BR ps (1)
> +may alternatively (or additionally) use
> +.IR /proc/ pid /cmdline.
> +.IP
>   Strings longer than
>   .B TASK_COMM_LEN
>   (16) characters (including the terminating null byte) are silently truncated.

-- 
<http://www.alejandro-colomar.es/>

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-12-28 20:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-23 17:59 [PATCH 0/2] proc.5: note broken v4.18 userspace promise Ævar Arnfjörð Bjarmason
2022-12-23 17:59 ` [PATCH 1/2] proc.5: note that "cmdline" might be favored over "stat.comm" by ps(1) Ævar Arnfjörð Bjarmason
2022-12-28 20:27   ` Alejandro Colomar [this message]
2022-12-23 17:59 ` [PATCH 2/2] proc.5: the "comm" field can be longer than 16 bytes Ævar Arnfjörð Bjarmason
2022-12-23 18:12 ` [PATCH 0/2] proc.5: note broken v4.18 userspace promise Linus Torvalds
2022-12-28 20:26   ` Alejandro Colomar
2023-01-04 20:59     ` Ævar Arnfjörð Bjarmason
2023-01-04 17:19   ` Tejun Heo

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=6f424f4b-6fa2-488d-74c9-0e66199baa07@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=adobriyan@gmail.com \
    --cc=alx@kernel.org \
    --cc=avarab@gmail.com \
    --cc=csmall@enc.com.au \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    --cc=tj@kernel.org \
    --cc=torvalds@linux-foundation.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