From: mathieu.desnoyers@efficios.com (Mathieu Desnoyers)
Subject: [ltt-dev] [RFC] lttng-tools command line interface
Date: Wed, 8 Jun 2011 17:46:41 -0400 [thread overview]
Message-ID: <20110608214641.GA30561@Krystal> (raw)
In-Reply-To: <4DEEC8CF.1050006@polymtl.ca>
* Alexandre Montplaisir (alexandre.montplaisir at polymtl.ca) wrote:
> 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?
This is what is printed with or without parameters.
> If yes, what is the default session name?
Maybe David has ideas on this ? I'm thinking along:
trace-$(date)
> 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?
good point, will add.
> ? 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.
Yes, we wanted to get the long options right first, and let David figure
out the shortcuts ;)
>
>> Comments are immensely welcome!
>>
>> Thanks,
>>
>> Mathieu
>>
>
> Looks great! Can't wait to try it!
Me too !
Thanks for the feedback,
Mathieu
>
> --
> Alexandre Montplaisir
> DORSAL lab,
> ?cole Polytechnique de Montr?al
>
--
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com
next prev parent reply other threads:[~2011-06-08 21:46 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
2011-06-08 21:46 ` Mathieu Desnoyers [this message]
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=20110608214641.GA30561@Krystal \
--to=mathieu.desnoyers@efficios.com \
/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