Fix tracing discovery of a non-secure participant
Use DISCOVERY instead of INFO (which ends up in the log, and so by default on stderr). Signed-off-by: Erik Boasson <eb@ilities.com>
This commit is contained in:
parent
b81ef4042b
commit
3c407a5d68
1 changed files with 1 additions and 1 deletions
|
@ -4734,7 +4734,7 @@ void new_proxy_participant
|
|||
*/
|
||||
entidx_insert_proxy_participant_guid (gv->entity_index, proxypp);
|
||||
add_proxy_builtin_endpoints(gv, ppguid, proxypp, timestamp);
|
||||
DDS_CLOG (DDS_LC_INFO, &gv->logconfig, "Un-secure participant "PGUIDFMT" tries to connect.\n", PGUID (*ppguid));
|
||||
ELOGDISC (proxypp, "Un-secure participant "PGUIDFMT" tries to connect.\n", PGUID (*ppguid));
|
||||
}
|
||||
#else
|
||||
/* Proxy participant must be in the hash tables for new_proxy_{writer,reader} to work */
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue