From: Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.COM>
To: Supervision <supervision@list.skarnet.org>
Subject: Re: [RFC] prctl: (Please do not!) Deprecate non PR_SET_MM_MAP operations
Date: Sun, 20 May 2018 14:36:02 +0100 [thread overview]
Message-ID: <9329a166-7295-8d66-9e12-b31abc887724@NTLWorld.COM> (raw)
In-Reply-To: <c8d4aa19-1bb4-3f72-4600-8d20fdad98d9@NTLWorld.COM>
In case you weren't aware, programs can make use of a facility on Linux
to make their ps listings contain appropriate command-line arguments and
environment strings. There's also a similar kernel API on FreeBSD. This
is used by the built-ins in nosh to good effect, even more so in the
forthcoming version 1.38, allowing system adminstrators to debug things
more easily from ps listings by showing them the actually effective
states of the chained argument and environment vectors rather than what
they were at the beginning of a chain of built-in commands.
* https://unix.stackexchange.com/a/438007/5132
* https://unix.stackexchange.com/a/432681/5132
The subject of deprecating and removing the API that permits this came
up recently on the Linux Kernel Mailing List. I raised my concerns, and
the Linux Kernel developers have been laudably responsive on the
subject. As I said to them, I would welcome a better API, that allows
setting these things atomically, start and length together as a pair.
* https://lkml.org/lkml/2018/4/3/739
* https://lkml.org/lkml/2018/5/6/127
* https://lkml.org/lkml/2018/5/7/78
* https://lkml.org/lkml/2018/5/7/79
* https://lkml.org/lkml/2018/5/7/80
* https://lkml.org/lkml/2018/5/7/81
next parent reply other threads:[~2018-05-20 13:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c8d4aa19-1bb4-3f72-4600-8d20fdad98d9@NTLWorld.COM>
2018-05-20 13:36 ` Jonathan de Boyne Pollard [this message]
[not found] <c8d4aa19-1bb4-3f72-4600-8d20fdad98d9@ntlworld.com>
[not found] ` <9329a166-7295-8d66-9e12-b31abc887724@ntlworld.com>
2018-05-20 15:57 ` Laurent Bercot
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=9329a166-7295-8d66-9e12-b31abc887724@NTLWorld.COM \
--to=j.deboynepollard-newsgroups@ntlworld.com \
--cc=supervision@list.skarnet.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;
as well as URLs for NNTP newsgroup(s).