From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Phil Sutter <phil@nwl.cc>
Cc: netfilter-devel@vger.kernel.org, Florian Westphal <fw@strlen.de>
Subject: Re: [nft PATCH RFC] monitor: Support printing processes which caused the event
Date: Wed, 10 May 2017 13:34:38 +0200 [thread overview]
Message-ID: <20170510113438.GA29824@salvia> (raw)
In-Reply-To: <20170510105510.891-1-phil@nwl.cc>
On Wed, May 10, 2017 at 12:55:10PM +0200, Phil Sutter wrote:
> This adds support for printing the process ID and name for changes which
> 'nft monitor' reports:
>
> | nft -a -p monitor
> | add chain ip t2 bla3 # pid 11616 (nft)
>
> If '-n' was given in addition to '-p', parsing the process name from
> /proc/<pid>/cmdline is suppressed.
That is not the process ID, that is the netlink portID, that is pretty
much useless if we get a robot process with multiple netlink sockets
(likely given that it may want to lookup from interface index to
interface name).
next prev parent reply other threads:[~2017-05-10 11:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-10 10:55 [nft PATCH RFC] monitor: Support printing processes which caused the event Phil Sutter
2017-05-10 11:27 ` Florian Westphal
2017-05-10 11:38 ` Pablo Neira Ayuso
2017-05-10 11:57 ` Florian Westphal
2017-05-10 14:39 ` Phil Sutter
2017-05-10 14:54 ` Florian Westphal
2017-05-10 15:11 ` Phil Sutter
2017-05-10 17:59 ` Florian Westphal
2017-05-11 6:41 ` Pablo Neira Ayuso
2017-05-11 6:59 ` Florian Westphal
2017-05-11 8:27 ` Phil Sutter
2017-05-11 9:58 ` Pablo Neira Ayuso
2017-05-11 9:59 ` Pablo Neira Ayuso
2017-05-10 11:34 ` Pablo Neira Ayuso [this message]
2017-05-10 12:52 ` Arturo Borrero Gonzalez
2017-05-10 14:02 ` Phil Sutter
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=20170510113438.GA29824@salvia \
--to=pablo@netfilter.org \
--cc=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=phil@nwl.cc \
/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).