From: Ben Hutchings <ben@decadent.org.uk>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@elte.hu>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Cc: 632923@bugs.debian.org, Christian Ohm <chr.ohm@gmx.net>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Bug#632923: linux-tools-2.6.39: perf tries to read ./config, fails if it is not a perf config file
Date: Thu, 07 Jul 2011 04:55:13 +0100 [thread overview]
Message-ID: <1310010913.4280.36.camel@localhost> (raw)
In-Reply-To: <20110707024506.GA32088@moongate.localnet>
[-- Attachment #1: Type: text/plain, Size: 804 bytes --]
On Thu, 2011-07-07 at 04:45 +0200, Christian Ohm wrote:
> Package: linux-tools-2.6.39
> Version: 2.6.39-3
> Severity: normal
>
> Hello,
>
> When running perf, it looks for a config file in /etc/perfconfig,
> ~/.perfconfig, and ./config (according to strace). If ./config is not a
> perf configuration, it fails (or possibly does unexpected things). Since
> "config" is a quite generic name (I have 175 files with that name on my
> system) it would be nice if this is changed to e.g. ./.perfconfig.
This indeed seems like a misfeature.
Is perf supposed to be invoked in directories dedicated to its use? If
not, why should it expect a generically-named file to belong to it?
Ben.
--
Ben Hutchings
The most exhausting thing in life is being insincere. - Anne Morrow Lindberg
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next parent reply other threads:[~2011-07-07 3:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110707024506.GA32088@moongate.localnet>
2011-07-07 3:55 ` Ben Hutchings [this message]
2011-08-05 16:58 ` [PATCH] perf: do not look at ./config for configuration Jonathan Nieder
2011-08-05 17:34 ` Arnaldo Carvalho de Melo
2011-08-10 8:26 ` [tip:perf/urgent] perf tools: " tip-bot for Jonathan Nieder
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=1310010913.4280.36.camel@localhost \
--to=ben@decadent.org.uk \
--cc=632923@bugs.debian.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=chr.ohm@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.