From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Chris Phlipot <cphlipot0@gmail.com>
Cc: adrian.hunter@intel.com, mingo@redhat.com, peterz@infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/5] perf script: fix postgresql ubuntu install instructions
Date: Tue, 19 Apr 2016 10:41:07 -0300 [thread overview]
Message-ID: <20160419134107.GD3677@kernel.org> (raw)
In-Reply-To: <1461056164-14914-3-git-send-email-cphlipot0@gmail.com>
Em Tue, Apr 19, 2016 at 01:56:02AM -0700, Chris Phlipot escreveu:
> The current instructions for setting up an Ubuntu system for using
> the export-to-postgresql.py script are incorrect.
>
> The instructions in the script have been updated to work on newer
> versions of ubuntu.
>
> -Add missing dependencies to apt-get command:
> python-pyside.qtsql, libqt4-sql-psql
> -Add '-s' option to createuser command to force the user to be a
> superuser since the command doesn't prompt as indicated in the
> current instructions.
>
> Tested on: Ubuntu 14.04, Ubuntu 16.04(beta)
Applied.
> Signed-off-by: Chris Phlipot <cphlipot0@gmail.com>
> ---
> tools/perf/scripts/python/export-to-postgresql.py | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/tools/perf/scripts/python/export-to-postgresql.py b/tools/perf/scripts/python/export-to-postgresql.py
> index 1b02cdc..6f0ca68 100644
> --- a/tools/perf/scripts/python/export-to-postgresql.py
> +++ b/tools/perf/scripts/python/export-to-postgresql.py
> @@ -34,10 +34,9 @@ import datetime
> #
> # ubuntu:
> #
> -# $ sudo apt-get install postgresql
> +# $ sudo apt-get install postgresql python-pyside.qtsql libqt4-sql-psql
> # $ sudo su - postgres
> -# $ createuser <your user id here>
> -# Shall the new role be a superuser? (y/n) y
> +# $ createuser -s <your user id here>
> #
> # An example of using this script with Intel PT:
> #
> --
> 2.7.4
next prev parent reply other threads:[~2016-04-19 13:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 8:56 [PATCH 1/5] perf tools: fix incorrect ordering of callchain entries Chris Phlipot
2016-04-19 8:56 ` [PATCH 2/5] perf script: extend db-export api to include callchains for samples Chris Phlipot
2016-04-22 7:56 ` Adrian Hunter
2016-04-23 4:41 ` Chris Phlipot
2016-04-28 8:36 ` Chris Phlipot
2016-04-19 8:56 ` [PATCH 3/5] perf script: fix postgresql ubuntu install instructions Chris Phlipot
2016-04-19 13:41 ` Arnaldo Carvalho de Melo [this message]
2016-04-23 13:03 ` [tip:perf/core] perf script: Fix " tip-bot for Chris Phlipot
2016-04-19 8:56 ` [PATCH 4/5] perf script: add option to control callchain export from python Chris Phlipot
2016-04-19 8:56 ` [PATCH 5/5] perf script: Update export-to-postgresql to support callchains Chris Phlipot
2016-04-22 7:55 ` [PATCH 1/5] perf tools: fix incorrect ordering of callchain entries Adrian Hunter
2016-04-22 7:59 ` Adrian Hunter
2016-04-23 3:35 ` Chris Phlipot
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=20160419134107.GD3677@kernel.org \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=cphlipot0@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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