Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: jeremie.galarneau@efficios.com (Jérémie Galarneau)
Subject: [lttng-dev] [PATCH lttng-tools] Fix: Some corrections to the lttng man page
Date: Tue, 5 Nov 2013 20:25:12 -0500	[thread overview]
Message-ID: <CA+jJMxsfyhffdEVEybjWA-5arfetSNbM9XuZXZN5r7mKX2xEEg@mail.gmail.com> (raw)
In-Reply-To: <48CF5AC71E61DB46B70D0F388054EFFD267A10D1@VAL-E-01.valcartier.drdc-rddc.gc.ca>

On Tue, Nov 5, 2013 at 4:34 PM, Thibault, Daniel <
Daniel.Thibault at drdc-rddc.gc.ca> wrote:

>  *De :* jeremie.galarneau at gmail.com
> *Envoy? :* 5 novembre 2013 15:51
>
>  On Thu, Oct 24, 2013 at 12:09 PM, Thibault, Daniel <
> Daniel.Thibault at drdc-rddc.gc.ca> wrote:
>
> -----Message d'origine-----
> Date: Wed, 23 Oct 2013 12:08:47 -0400
> From: J?r?mie Galarneau <jeremie.galarneau@efficios.com>
>
> > diff --git a/doc/man/lttng.1 b/doc/man/lttng.1
> > [...]
>
> > +All user-space applications instrumented with lttng-ust(3) will
> > automatically register to the session daemon. This feature gives you the
> > ability to list available traceable applications and tracepoints on a
> per user
> > basis. (See \fBlist\fP command).
>
>    Is this a statement of intent?  LTTng 2.3.0's list command identifies
> user-space events by trace provider name, event name, and process ID, but
> not by user ID (in fact it doesn't even yet filter the kernel events out
> when one asks for 'list -u session'; see bug #654).  And there is as yet no
> way to filter the 'lttng list' output by user ID (an optional argument for
> the -u option could do the trick).
>
>     Of course, listing available tracepoints is automatically per-user
> when using a local session daemon.  But if you're a member of the
> 'tracing' group, you'll deal exclusively with the root daemon and won't
> have that choice.
>
>  > I didn't change the meaning of the original sentence. It just means
> that "lttng list" will output the events registered to the user's
> corresponding session daemon.
>
> > Perhaps you can suggest a better phrasing?
>
> >
>
> > J?r?mie
>
>
>
>    How about this?
>
>
>
> Each user-space application instrumented with lttng-ust(3) will
> automatically
>
> register with the root session daemon and its user session daemon. This
> allows
>
> each daemon to list the available traceable applications and tracepoints
> at
>
> any given moment (See the \fBlist\fP command).
>
>
>

Looks good to me.

Cheers,
J?r?mie


>  (There is no need to explain further the diff between the two daemons
> since the preceding paragraph in the man page already talks about
> co-existing session daemons)
>
>
>
> Daniel U. Thibault
> Protection des syst?mes et contremesures (PSC) | Systems Protection &
> Countermeasures (SPC)
> Cyber s?curit? pour les missions essentielles (CME) | Mission Critical
> Cyber Security (MCCS)
> R & D pour la d?fense Canada - Valcartier (RDDC Valcartier) | Defence R&D
> Canada - Valcartier (DRDC Valcartier)
> 2459 route de la Bravoure
> Qu?bec QC  G3J 1X5
> CANADA
> Vox : (418) 844-4000 x4245
> Fax : (418) 844-4538
> NAC : 918V QSDJ <http://www.travelgis.com/map.asp?addr=918V%20QSDJ> <*http://www.travelgis.com/map.asp?addr=918V%20QSDJ
> <http://www.travelgis.com/map.asp?addr=918V%20QSDJ>*>
> Gouvernement du Canada | Government of Canada
> <http://www.valcartier.drdc-rddc.gc.ca/>
>



-- 
J?r?mie Galarneau
EfficiOS Inc.
http://www.efficios.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lttng.org/pipermail/lttng-dev/attachments/20131105/40ebef8a/attachment-0001.html>


  reply	other threads:[~2013-11-06  1:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <48CF5AC71E61DB46B70D0F388054EFFD2679FA2C@VAL-E-01.valcartier.drdc-rddc.gc.ca>
2013-11-05 20:50 ` Jérémie Galarneau
2013-11-05 21:34   ` Thibault, Daniel
2013-11-06  1:25     ` Jérémie Galarneau [this message]
2014-02-03 16:05       ` 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=CA+jJMxsfyhffdEVEybjWA-5arfetSNbM9XuZXZN5r7mKX2xEEg@mail.gmail.com \
    --to=jeremie.galarneau@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