From: Bernhard Voelker <mail@bernhard-voelker.de>
To: kerolasa@gmail.com
Cc: "Sami Kerola" <kerolasa@iki.fi>, "Karel Zak" <kzak@redhat.com>,
"Mantas Mikulėnas" <grawity@gmail.com>,
util-linux@vger.kernel.org
Subject: Re: lslocks – "failed to parse pid: 'WRITE'"
Date: Tue, 12 Feb 2013 12:56:10 +0100 [thread overview]
Message-ID: <511A2DDA.40504@bernhard-voelker.de> (raw)
In-Reply-To: <CAG27Bk109veDrkVetXg5cRSA0TogpbhJ0PwFArRyf=pqQg0zfQ@mail.gmail.com>
On 02/12/2013 12:23 PM, Sami Kerola wrote:
> Almost off topic.
while we're at it - ;-)
is it necessary to open/read/close "/proc/self/mountinfo" so often?
$ strace -e open ./lslocks 2>&1 | grep mountinfo | wc -l
67
Have a nice day,
Berny
next prev parent reply other threads:[~2013-02-12 11:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-07 14:42 lslocks – "failed to parse pid: 'WRITE'" Mantas M.
2013-02-11 22:42 ` Sami Kerola
2013-02-11 23:23 ` Mantas Mikulėnas
2013-02-12 11:12 ` Karel Zak
2013-02-12 11:23 ` Sami Kerola
2013-02-12 11:56 ` Bernhard Voelker [this message]
2013-02-12 13:18 ` Karel Zak
2013-02-14 15:02 ` Karel Zak
2013-02-12 13:20 ` Karel Zak
2013-02-14 15:44 ` Karel Zak
2013-02-12 10:35 ` Karel Zak
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=511A2DDA.40504@bernhard-voelker.de \
--to=mail@bernhard-voelker.de \
--cc=grawity@gmail.com \
--cc=kerolasa@gmail.com \
--cc=kerolasa@iki.fi \
--cc=kzak@redhat.com \
--cc=util-linux@vger.kernel.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