aboutsummaryrefslogtreecommitdiffstats
path: root/Transceiver52M
diff options
context:
space:
mode:
authorPau Espin Pedrol <pespin@sysmocom.de>2019-09-17 20:26:53 +0200
committerPau Espin Pedrol <pespin@sysmocom.de>2019-10-09 19:15:49 +0200
commitb7e992703c285fa8ea1f22b970d4aa1f202720eb (patch)
treea2897d9ffb05ea82b665dbfdbfb85590a560e225 /Transceiver52M
parent928141b7d682a80b12875ef5d288646755dba44e (diff)
Use new libosmocore logging lock API
Since libosmocore Id7711893b34263baacac6caf4d489467053131bb, a new API log_enable_multithread() is available which takes care of protecting logging infrastructure from us (and actually does it correctly since we cannot protect internal libosmocore structures from osmo-trx). Let's drop all mutex related code from osmo-trx logging infra and simply rely on libosmocore's. Related: OS#4088 Change-Id: I519d0f30bce871005ca26b90177ea4aa4839360a
Diffstat (limited to 'Transceiver52M')
-rw-r--r--Transceiver52M/osmo-trx.cpp5
1 files changed, 1 insertions, 4 deletions
diff --git a/Transceiver52M/osmo-trx.cpp b/Transceiver52M/osmo-trx.cpp
index 9fe6585..6b83988 100644
--- a/Transceiver52M/osmo-trx.cpp
+++ b/Transceiver52M/osmo-trx.cpp
@@ -576,14 +576,11 @@ int main(int argc, char *argv[])
printf("Built without atomic operation support. Using Mutex, it may affect performance!\n");
#endif
- if (!log_mutex_init()) {
- fprintf(stderr, "Failed to initialize log mutex!\n");
- exit(2);
- }
convolve_init();
convert_init();
osmo_init_logging2(tall_trx_ctx, &log_info);
+ log_enable_multithread();
osmo_stats_init(tall_trx_ctx);
vty_init(&g_vty_info);
ctrl_vty_init(tall_trx_ctx);