From: "Laurent Bercot" <ska-supervision@skarnet.org>
To: "Jonathan de Boyne Pollard"
<J.deBoynePollard-newsgroups@ntlworld.com>,
Supervision <supervision@list.skarnet.org>
Subject: Re: s6-ps
Date: Sat, 05 Jan 2019 00:20:51 +0000 [thread overview]
Message-ID: <em73ca7ad9-ddf4-4441-a37c-e953aa35cf85@elzian> (raw)
In-Reply-To: <9f647c4c-2dc3-b977-928c-ee164ba88afe@ntlworld.com>
>It occurs to me that s6-ps would gain from having an "exe" column.
That functionality:
- isn't available in procps. I modelled the available columns from
procps' ones. Although that doesn't mean much, because there are many
more columns available now in recent versions of procps than there are
in s6-ps.
- requires an extra system call per process: a readlinkat() on "exe".
I tried to limit the functionality to what can be read in the "stat"
file. Using "comm" as well was unavoidable, but annoying.
That said, if there's demand for it, I'm not opposed to adding a
column for exe. I just wasn't aware of people besides me actually using
s6-ps. :)
--
Laurent
next parent reply other threads:[~2019-01-05 0:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9f647c4c-2dc3-b977-928c-ee164ba88afe@ntlworld.com>
2019-01-05 0:20 ` Laurent Bercot [this message]
2019-01-05 4:04 ` s6-ps Jonathan de Boyne Pollard
2019-01-05 10:46 ` s6-ps Jonathan de Boyne Pollard
2019-01-05 14:41 ` s6-ps Jonathan de Boyne Pollard
2019-01-05 15:29 ` s6-ps multiplexd
2019-01-05 20:30 ` Can s6 be enough?: was s6-ps Steve Litt
2019-01-05 21:22 ` Laurent Bercot
[not found] ` <20190106053901.GA16647@latitude.localdomain>
2019-01-06 7:40 ` Laurent Bercot
2019-01-06 15:03 ` Brett Neumeier
2019-01-07 21:45 ` Steve Litt
2019-01-08 9:19 ` Laurent Bercot
2019-01-05 21:00 ` s6-ps Guillermo
2019-01-06 1:15 ` s6-ps Steve Litt
2019-01-06 7:06 ` s6-ps Colin Booth
2019-01-06 7:30 ` s6-ps Laurent Bercot
2019-01-06 18:07 ` s6-ps Colin Booth
2019-01-04 9:18 s6-ps Jonathan de Boyne Pollard
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=em73ca7ad9-ddf4-4441-a37c-e953aa35cf85@elzian \
--to=ska-supervision@skarnet.org \
--cc=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).