laforge submitted this change.

View Change

Approvals: Jenkins Builder: Verified laforge: Looks good to me, approved
server: Clarify reason of rolling pcap due to max-file-size vty config

Change the logging to print the VTY config name, so user can relate the
exct string, otherwise it can be confusing.

Related: SYS#7842
Change-Id: I6d2a2217e556afeedad78a1e9217f6a448d674c0
---
M src/osmo_server_core.c
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/osmo_server_core.c b/src/osmo_server_core.c
index 4dc4178..a13c64c 100644
--- a/src/osmo_server_core.c
+++ b/src/osmo_server_core.c
@@ -393,7 +393,7 @@
if (conn->wrf->wr_offset + data_len <= conn->server->max_size)
return false;

- LOGP(DSERVER, LOGL_NOTICE, "Rolling over file for %s (max-size)\n", conn->name);
+ LOGP(DSERVER, LOGL_NOTICE, "Rolling over file for %s (max-file-size)\n", conn->name);
osmo_pcap_conn_restart_trace(conn);
return true;
}

To view, visit change 41951. To unsubscribe, or for help writing mail filters, visit settings.

Gerrit-MessageType: merged
Gerrit-Project: osmo-pcap
Gerrit-Branch: master
Gerrit-Change-Id: I6d2a2217e556afeedad78a1e9217f6a448d674c0
Gerrit-Change-Number: 41951
Gerrit-PatchSet: 1
Gerrit-Owner: pespin <pespin@sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: laforge <laforge@osmocom.org>