Fix: do not return error on LTTNG_ERR_SNAPSHOT_NODATA
A warning is fine since the user has no control on
whether or not applications (or the kernel) have
produced any event between the start of the tracing
session and the recording of the snapshot.
MI wise the command is not a success since nothing was
recorded. The command line return code is CMD_SUCCESS.
84f4ce0...
by
=?utf-8?q?J=C3=A9r=C3=A9mie_Galarneau?= <email address hidden>
Fix: Set loopback adress in set_ip_addr if gethostbyname2 fails
Some systems may not have "localhost" defined in accordance with IETF
RFC 6761. According to this RFC, applications may recognize
"localhost" names as special and resolve to the appropriate loopback
address.
We choose to use the system name resolution API first to honor its
network configuration. If this fails, we resolve to the appropriate
loopback address. This is done to accomodate systems which may want to
start tracing before their network configured.
Fix: load event state (enabled/disabled) correctly
This bug fix is a workaround due to limitations of lttng_disable_event_ext
regarding the disabling of events with similar name but different
characteristics. Although lttng_disable_event_ext provides support for
disabling by name and filter string it does not support exclusion.
The loading of events is cut in 3 phases.
1 - Create all events regardless of their state.
2 - Disable all events.
3 - Enable only the events with the 'enabled' state.
