Skip to content
[Jenkins]Jenkins
log insign up
Success

Changes

Summary

  1. stream: Explicitly document MSG_NOTIFICATION case in recv() API (details)
  2. stream: Improve logging around recv() failure (details)
  3. stream_cli: Log all code paths ending up in close/reconnect (details)
  4. stream_cli: Announce failed connect() if reconnect is disabled (details)
Commit 0b87970bf6d1946eda7b1e9b7746e8a698f8e336 by Pau Espin Pedrol
stream: Explicitly document MSG_NOTIFICATION case in recv() API

Change-Id: I4fa70ae3f704d2379982153b5630009c13a6f316
The file was modifiedsrc/stream_cli.c
The file was modifiedsrc/stream_srv.c
Commit c878794473dd7c7c8ff286337ee01f9c726adb03 by Pau Espin Pedrol
stream: Improve logging around recv() failure

Change-Id: Ic050e7141b029d984fbbcc76ffc175f8e6b01664
The file was modifiedsrc/stream_cli.c
The file was modifiedsrc/stream_srv.c
Commit 2e6325ae412b5f412cb8fcb34fd71e988c1b9fc3 by Pau Espin Pedrol
stream_cli: Log all code paths ending up in close/reconnect

This way it's possible to track why a connection was closed od/and
reconnected (depending on reconnect config set by user).

Change-Id: I6debc5de193d99919fe858befd905223ef965d81
The file was modifiedsrc/stream_cli.c
Commit e6c09ffa973517a580a42134694c1812efe18a2a by Pau Espin Pedrol
stream_cli: Announce failed connect() if reconnect is disabled

One of the use cases of disabling reconnect in osmo_stream_cli is
because the user of the stream wants to control the reconnect based on
upper layer contexts. In this case, though, if there's a failure during
connect() time, the user won't get any notification and hence stay
disconnected forever. Instead, inform the user through the
disconnect_cb().

Change-Id: I69a5f7c3c7cea97d31e2fa03e8c32ce806285eb6
The file was modifiedsrc/stream_cli.c