From: nils.carlson@ludd.ltu.se (Nils Carlson)
Subject: [ltt-dev] [UST] ustctl cli
Date: Thu, 4 Nov 2010 20:37:44 +0100 [thread overview]
Message-ID: <510B9F4C-E2E6-4A35-863C-EBE48E361F2C@ludd.ltu.se> (raw)
In-Reply-To: <4CD03B4E.5000205@polymtl.ca>
On Nov 2, 2010, at 5:24 PM, David Goulet wrote:
> Hi again,
>
> Yes!
>
> # ustctl enable <CHANNEL> <MARKER>
> # ustctl set-path <NEW_PATH>
> ...
>
> Although, since tracing session is the next step (actually ongoing),
> it might be good to have something like that ? :
>
> # ustctl trace1_name <OPTIONS> <COMMAND>
>
Yepp, though I would reorder it a bit, maybe more like
ustctl create-trace nils_trace
ustctl enable-marker nils_trace sendmsg_marker
ustctl bufsize nils_trace ust 2MB
or something like that...
But I have to admit I've been working with switches lately which all
have nice custom CLI's with tab based help and command expansion and
stuff so I'm a bit spoiled.
/Nils
> (And for the options, I will go with lttctl that I think is better :)
> -o, --option OPTION
> Set options, following operations are supported:
> channel.<channelname>.enable=
> channel.<channelname>.overwrite=
> channel.<channelname>.bufnum=
> channel.<channelname>.bufsize=
> <channelname> can be set to all for all channels
> channel.<channelname>.switch_timer= (timer interval in ms)
>
> In any case, for usability, we should come up with something else
> then long option like --enable-marker, --get-subbuf-size, ...
>
> What do you think? Maybe telling us a bit what's your idea.
>
> David
>
> On 10-11-01 11:06 AM, Nils Carlson wrote:
>> I've been thinking about the ustctl cli lately. Mostly because I
>> need to
>> add trace names to a lot of commands. The current api doesn't really
>> provide an obvious way forward. What I'm going to do first is just
>> try
>> hack it in.
>>
>> In the long-term though I'm wondering if we should move to something
>> more elegant, more like git or route? What do people think?
>>
>> /Nils
>>
>> _______________________________________________
>> ltt-dev mailing list
>> ltt-dev at lists.casi.polymtl.ca
>> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
>
> --
> David Goulet
> LTTng project, DORSAL Lab.
>
> PGP/GPG : 1024D/16BD8563
> BE3C 672B 9331 9796 291A 14C6 4AF7 C14B 16BD 8563
>
> _______________________________________________
> ltt-dev mailing list
> ltt-dev at lists.casi.polymtl.ca
> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
prev parent reply other threads:[~2010-11-04 19:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-01 15:06 Nils Carlson
2010-11-02 16:24 ` David Goulet
2010-11-04 19:37 ` Nils Carlson [this message]
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=510B9F4C-E2E6-4A35-863C-EBE48E361F2C@ludd.ltu.se \
--to=nils.carlson@ludd.ltu.se \
/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