Hi Jérémie,
My name is Vamshi Pulluri and I am a Master's student in Telecommunication from
KTH Royal Institute of Technology, Stockholm. I am using LTTng for tracing the
streams in RAN architecture. I wanted to use LTTng trace viewer, Babeltrace,
for viewing in live mode and then came across
In case of a per-UID buffer, events following a change of user ID should be
forwarded to buffers of the new UID. In order to do so, we add a wrapper around
setuid(3), setreuid(3) and setresuid(2) that unregister and re-register the
application from the session daemon.
While there exist some other
Hello,
That's an interesting feature.
On 2019-06-11 11:57 a.m., Gabriel-Andrew Pollo-Guilbert wrote:
> In case of a per-UID buffer, events following a change of user ID should be
> forwarded to buffers of the new UID. In order to do so, we add a wrapper
> around
> setuid(3), setreuid(3) and set
This test requires liblttng-ust-setuid library wrapper around the family of
setuid() system calls. In per-UID mode, it makes sure that events following
one of these system calls are put in the correct buffers.
The test is destructive as it may add new users to the system and modify
their groups. I
The teardown of a ring buffer causes a number of diagnostic messages
to be printed to using printk. One of those contains the "records
count", which is only updated when lttng-modules is built with
LTTNG_RING_BUFFER_COUNT_EVENTS defined.
Move the "records count" printing to a different function an
Hi,
These releases to the LTTng 2.9 and 2.10 stable branches, as well
as the release candidate for the LTTng 2.11 branch, contain a
series of bugfixes, and adds support for the 5.1 and 5.2-rc Linux
kernels.
One user-impacting fix is the following:
"Fix: don't access packet header for stream_id a
