Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: alexandre.montplaisir@polymtl.ca (Alexandre Montplaisir)
Subject: [ltt-dev] [RFC] lttng-tools command line interface
Date: Tue, 07 Jun 2011 20:56:47 -0400	[thread overview]
Message-ID: <4DEEC8CF.1050006@polymtl.ca> (raw)
In-Reply-To: <20110607230851.GA1208@Krystal>

Very nice!


Some dumb questions:

On 11-06-07 07:08 PM, Mathieu Desnoyers wrote:
> ... the elements below between [ ] are
> actually optional, not "implied by default" as stated above.
>

> * Tracing session control
>
> lttng create [--session name] # create a tracing session
>       [--output path]          # optionally specify the output path
>       [--name name]            # optional session name (default provided)
>
> --->  This command prints
>       "Working directory of created session is /path/to/name. Change your"
>       "current working directory to interact with this session."

Is this what is printed if only "lttng create" with no parameters is 
typed in?
If yes, what is the default session name?
If not, I guess it prints the same as "lttng create --help" ?

>
> --->  All the following commands use the current working directory
>       .lttng/config file to keep track of the session on which actions
>       should be applied.

Yup, Git-alike  ;)

>
> lttng destroy [--session name] # teardown a tracing session
> lttng start [--session name]   # start tracing for a session
> lttng stop [--session name]    # stop tracing for a session

Is "--session" needed here, or would just "lttng destroy mysession" be 
allowed/wanted too?
? la "git push origin master", which does not require any --options for 
mandatory parameters, only extras.

>
> lttng add-context name --kernel [--event name] [--channel name] --type context_type [context options]
> lttng add-context name --userspace [--event name] [--channel name] [--all/--pid n/cmd_name] --type context_type [context options]

I guess you have plans for short options too? like,
-k, --kernel
-u, --userspace
-e, --event
etc.

> Comments are immensely welcome!
>
> Thanks,
>
> Mathieu
>

Looks great! Can't wait to try it!

-- 
Alexandre Montplaisir
DORSAL lab,
?cole Polytechnique de Montr?al





  parent reply	other threads:[~2011-06-08  0:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-07 23:08 Mathieu Desnoyers
2011-06-07 23:19 ` Mathieu Desnoyers
2011-06-08  0:56 ` Alexandre Montplaisir [this message]
2011-06-08 21:46   ` Mathieu Desnoyers
2011-06-08  8:02 ` Stefan Hajnoczi
2011-06-08 21:49   ` Mathieu Desnoyers

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=4DEEC8CF.1050006@polymtl.ca \
    --to=alexandre.montplaisir@polymtl.ca \
    /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